• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Is Private Cloud Right for Your Organization
 

Is Private Cloud Right for Your Organization

on

  • 762 views

This is a presentation I did for a Focus webinar:

This is a presentation I did for a Focus webinar:
http://www.focus.com/webcasts/information-technology/private-cloud-right-your-organization/

Statistics

Views

Total Views
762
Views on SlideShare
762
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Elevator Pitch: ServiceMesh has been around since 2008 (really late 2007). If you wanted to really to simplify it… we’re a software company in the Cloud Mgmt space… although that’s a very limiting description. More accurately, what ServiceMesh really does is help large enterprises adopt what we call “Agile IT operating models”. (Cloud is part of this…but its much more than just cloud… which I’ll explain shortly). What this allows them to do is drastically reduce the money and resources consumed by their current IT operations and infrastructure, and instead redirect it so IT can become more innovative, more adaptable to business change, and even enable new business models. The way that we do that is by providing advisory services and a product platform that fully governs and manages federations of SaaS, PaaS, internal and external clouds providers to create an “everything-as-a-service” IT environment that is more agile and cost effective than what enterprises are using today. Our GTM approach is to lead with a series of (what we call) pre-packaged IT optimization strategies, that are basically solution accelerators, that provide a low-risk entry point…. and customer build upon these as stepping stones in a path toward this larger operating model transformation.As a company, we’ve been working on these challenges since 2008 with large enterprise customers…before cloud computing became such an overused buzzword. And we feel fortunate to have gotten a good head start on where IT is headed today with cloud… particularly from an enterprise perspective. Our customers are Global 2000… most with very complex, highly regulated, competitive environments….. Some with annual IT budgets exceeding $1B.The ServiceMesh team itself has acquired expertise in several areas working with these enterprise accounts. Not just in cloud technologies… but also IT strategy, architecture and design, platform integration, security, governance, organizational change management, and so on.ServiceMesh itself is a global company. We have customers in NA, EMEA, and AP. Austin is Dev center. LA contains a good portion of the exec mgmt team.
  • The considerable governance and lifecycle mgmt capabilities in the Agility Platform enable many of the core capabilities we just discussed. Those same capabilities are also critical for other cloud use cases. The Agility Platform is designed to provide a unified platform to govern and manage all of them. This provides additional benefits to manage the placement and schedule of all of these workload deployments.
  • Cost per VMCost comparisons to EC2Capacity unit optimizationVM density optimizationAutomated provisioningAuto-scalingDynamic security configurationThe physical infrastructure that include CPU, network, storage, and memory. The virtual environment runs on top of the CHP hardware and supports the IaaS and IPaaS offerings with interface with the security and management layer The CHP defines an optimised, standardised, high density, virtual infrastructure hosting configuration which is designed to meet price /performance benchmarks. CHP is optimized forPricePerformance (both bare metal and virtualized hosting)Rapid deploymentReduced complexityOptimizedfor virtualization, stateless computing, and hosting a large number of instancesDesigned for high density, low power and minimal heatThe same model can be used both internally and at external hosting providers, but it is not a requirement for the external hosting provider to utilize the architecture in order to provide computing supportThe IaaS offering can be either internal hosted or external hosted, and the compute support offering is the same under either model. Under the external private compute model, the hosting provider owns, manages and controls the underlying infrastructure, but CBA retains control over the OS, storage and deployed applications.CHP is deployed in modular units on standardised commodity hardware.The CHP defines an optimised, standardised, high density, virtual infrastructure hosting configuration which is designed to meet price /performance benchmarks. It does not necessarily define specific virtualisation software or underlying hardware manufactures.
  • Cost per VMCost comparisons to EC2Capacity unit optimizationVM density optimizationAutomated provisioningAuto-scalingDynamic security configurationThe physical infrastructure that include CPU, network, storage, and memory. The virtual environment runs on top of the CHP hardware and supports the IaaS and IPaaS offerings with interface with the security and management layer The CHP defines an optimised, standardised, high density, virtual infrastructure hosting configuration which is designed to meet price /performance benchmarks. CHP is optimized forPricePerformance (both bare metal and virtualized hosting)Rapid deploymentReduced complexityOptimizedfor virtualization, stateless computing, and hosting a large number of instancesDesigned for high density, low power and minimal heatThe same model can be used both internally and at external hosting providers, but it is not a requirement for the external hosting provider to utilize the architecture in order to provide computing supportThe IaaS offering can be either internal hosted or external hosted, and the compute support offering is the same under either model. Under the external private compute model, the hosting provider owns, manages and controls the underlying infrastructure, but CBA retains control over the OS, storage and deployed applications.CHP is deployed in modular units on standardised commodity hardware.The CHP defines an optimised, standardised, high density, virtual infrastructure hosting configuration which is designed to meet price /performance benchmarks. It does not necessarily define specific virtualisation software or underlying hardware manufactures.
  • The physical infrastructure that include CPU, network, storage, and memory. The virtual environment runs on top of the CHP hardware and supports the IaaS and IPaaS offerings with interface with the security and management layer The CHP defines an optimised, standardised, high density, virtual infrastructure hosting configuration which is designed to meet price /performance benchmarks. CHP is optimized forPricePerformance (both bare metal and virtualized hosting)Rapid deploymentReduced complexityOptimized for virtualization, stateless computing, and hosting a large number of instancesDesigned for high density, low power and minimal heatThe same model can be used both internally and at external hosting providers, but it is not a requirement for the external hosting provider to utilize the architecture in order to provide computing supportThe IaaS offering can be either internal hosted or external hosted, and the compute support offering is the same under either model. Under the external private compute model, the hosting provider owns, manages and controls the underlying infrastructure, but CBA retains control over the OS, storage and deployed applications.CHP is deployed in modular units on standardised commodity hardware.The CHP defines an optimised, standardised, high density, virtual infrastructure hosting configuration which is designed to meet price /performance benchmarks. It does not necessarily define specific virtualisation software or underlying hardware manufactures.

Is Private Cloud Right for Your Organization Is Private Cloud Right for Your Organization Presentation Transcript

  • Is Private Cloud Right for Your Organization?A 5-Step Litmus Test
    Dave Roberts
    Vice President, Strategy
    dave.roberts@servicemesh.com
    Company Twitter: @servicemesh
    Personal Twitter: @sandhillstrat
  • Who is ServiceMesh?
    • Provider of Agile IT governance, security and lifecycle management software and services for Global 2000 clients
    • Customers include some of the world’s largest and most sophisticated companies in:
    • Financial services
    • Health care
    • Consumer
    • Other IT-intensive industries
    • Global presence with headquarters in Los Angeles and offices in Austin, London, New York, Sydney, and Washington D.C.
    2
    3X revenue growth in 2010
    3rd consecutive year of profitability
  • “I Heard There’s No Such Thing as Private Cloud”
    Some large cloud service providers want to force the world into a one-size-fits-all, public cloud model.
    Anything that challenges that public cloud world-view must be attacked.
    FACT: Every G2000 enterprise that ServiceMesh is working with is building private clouds.
    FACT: The TM Forum’s Enterprise Cloud Leadership Council (ECLC) has defined requirements and a working group that encompasses private cloud (enterprise-grade IaaS).
    3
  • The World is Multi-Dimensional
    4
    Excess Capacity Sellback
    AWS EC2
    Public
    Internal ITorService Provider
    Savvis
    Private
    Internal
    External
  • Private vs. Virtual Private
    Public cloud vendors are retrenching and offering “virtual private cloud”
    Characteristics
    Shared infrastructure
    Private access via VPN
    Rich networking functionality
    Private IP address space makes it appear as part of the enterprise data center
    Question: Why would they do such a thing if private cloud didn’t exist?
    Answer: Because enterprises are demanding more than public clouds. But they want to leverage the infrastructure across multiple customers for higher efficiency.
    5
  • Hybrid Clouds Enable Optimization
    6
    • Optimize workload placement and schedule
    • Enable portability across clouds
    • Align best fit providers to unique needs
    • Drive price arbitrage between providers
    Virtual desktops
    (Day)
    Grid nodes (Night)
    Dev and test environments
    Dev and test environments
    Grid nodes (Day)
    Internal Private Cloud
    External Public Cloud
  • 7
    Private Cloud Litmus Test
    1
    Do you have specific securityrequirements?
    • Data in transit
    • Data at rest
    • Data destruction requirements
    • Audit requirements
    • Regulated industry
  • 8
    Private Cloud Litmus Test
    2
    Are you of sufficient scale?
    • Doesn’t make sense to build an optimized private cloud if you’re small
    • But don’t underestimate yourself
    • If you have 500 workloads or more, It might make sense to build a private cloud
  • 9
    Private Cloud Litmus Test
    3
    Do you have a reasonable fraction of dynamic workloads?
    • If your workloads are largely static, then you might be better off with traditional server or virtualization solutions
    • You might still want to outsource in a traditional managed hosting model
    • Or go hybrid here:“Buy the base, rent the peak”
  • 10
    Private Cloud Litmus Test
    4
    Can you deal with the organizational dynamicsassociated with the effort?
    • Building a private cloud is not simply a matter of purchasing and assembling technology
    • Shifting to a cloud operating model will require changes to processes and job roles
    • You’ll need sufficient top-down support to effect lasting change
  • 11
    Private Cloud Litmus Test
    5
    Do you have specialrequirements?
    • Predictable outcomes
    • Reserved capacity
    • Known performance (CPU, disk, network)
    • Known latencies
  • Basic Private Cloud Architecture Stack
    12
    Private Cloud Users
    Billing
    Workflow
    Policy and Governance
    Automation
    Security
    CloudAPI
    Hypervisor
    Private Cloud
    Pod
    External Public Cloud
    CPU
    Network
    Storage
    Private Cloud Pod
  • Pod Reference Implementation
    13
    • Infrastructure selection will vary based on specific organizational needs to provide the optimal combination of performance, cost, and simplicity.
    • Look for a balanced design that delivers the right ratio of CPU, storage, and network bandwidth.
    VM density:
    • 1600 server workloads per compute rack
    • 6000 desktop workloads per compute rack
    48 blades for a total of 576 cores. Standard memory config is 96 GB/blade, high end config is 192 GB/blade.
    Two 10 Gbps switches, each with 480 Gbps of network bandwidth.
    100 TB of raw storage capacity and 500 GB of memory.
    Other reference implementation metrics and technical specs are available.
  • The Need for Balance
    14
  • Pod Reference Implementation
    15
    • Based on published external cloud prices, financial analysis showed that the private cloud can cost up to 75% less than comparable external cloud offerings for a high-availability use-case.
    • End-to-end automation required only minutes to provision workload, auto-scale, and configure security for complex topologies, which normally would take days or weeks.
  • Adopt a Cloud Operating Model
    Private cloud is not a product or technology you can simply buy and install
    FAQ: “What’s the difference between virtualization and private cloud?”
    Answer: Virtualization is a technology used to build private clouds, but clouds are more about how you operate the technology and expose it to your users than the technologies themselves
    To extract the full advantage, you’ll need to run your internal private cloud like a (mini) service provider
    That means you’ll have to move from your traditional IT operating model to a cloud operating model
    To implement a cloud operating model, you’ll need to:
    Rework processes and procedures
    Define internal SKUs for your users
    Create SLAs
    Create internal pricing
    16
  • Creating Internal Private Cloud SKUs
    17
    Don’t forget this!Use it to fund maintenance, upgrades, continual development, and support.Think like a service provider. Run it like a business!
    Private Cloud SKU Price
    Internal Markup
    SKU Cost
    SKU Capacity
    Aggregate Pod Capacity
  • Understanding Contestability
    Explicit Goal: Make your private cloud earn its keep.
    To do this, you need to seek opportunities for “contestability”
    You want competition between your own private offering and others
    Other offerings might be other internal private clouds!
    Don’t create a private cloud and run it poorly!
    Don’t waste money on something that isn’t competitive
    Don’t settle for poor service
    18
  • 19
    Private Cloud Results
    Deploy Fast:
    Scale Faster:
    Provisioning with private cloud: 4 minutes
    Minutes
    Automated policy enforcement
    Start using it
    Self-service portal
    Provisioning with virtualization only: 3-6 weeks
    Number of simultaneous server instances provisioned
    IT approval
    Provision VM and configure
    VM request
    Start using it
    Provisioning with hardware procurement: 12-18 weeks
    Hardware requisition
    Procurement approval
    Hardware arrives
    Rack in data center
    Start using it
    Setup platform/ application
    * Reference implementation test results, Nov 2010