VMware – VMworld 2017 – LHC3371BUC – VMware Cloud on AWS – The Painless Path to Hybrid Cloud

Disclaimer: I recently attended VMworld 2017 – US.  My flights were paid for by ActualTech Media, VMware provided me with a free pass to the conference and various bits of swag, and Tech Field Day picked up my hotel costs. There is no requirement for me to blog about any of the content presented and I am not compensated in any way for my time at the event.  Some materials presented were discussed under NDA and don’t form part of my blog posts, but could influence future discussions.

Here are my rough notes from “LHC3371BUC – VMware Cloud on AWS – The Painless Path to Hybrid Cloud”, presented by Eric Hanselman (Chief Analyst, 451 Research) and Andy Reedy (Partner Solutions Architecture, AWS). You can grab a PDF or my notes here. Andy does the intro and then Eric takes the stage.

 

Infrastructure Change is Difficult

“In the middle of difficulty lies opportunity” – Albert Einstein

Infrastructure change is difficult

  • … but necessary
  • Competitive pressures
  • Resource contraints
  • Business requirements

We need to be able to manage our environments. 451 Research did a survey on expected cloud uptake. The shift of workloads to cloud environments over the next 2 years is dramatic, from 41% overall today to 60% expected in 2 years. Off-premises workloads will also move from 35% to 52% in two years, and cloud providers will account for 76% of all cloud workloads.

 

Hybrid Momentum

  • 32% single cloud
  • 32% multi-cloud
  • 22% multi-cloud + (integrated on and off-premises environments)
  • 15% Hybrid – single business function distributed to multiple execution venues

There’s a lot of technical debt in the enterprise and while the promise of hybrid cloud is really attractive, getting there is difficult.

 

Strategies

  • Targeted
  • New workloads
  • Internal / external
  • DR / continuity
  • Test / dev
  • “Bursting” (This one isn’t terribly practical for a lot of enterprise applications)
  • Repatriation

 

An Opportunity

  • Integrated cloud management platforms – alliances that change the equation
  • Addressing risks – 3 Ts – transition, training, transformation
  • Facilitating change – Buying options at low cost

Test and development Use Case

 

Integrated management benefits

  • Common tool chains – reduced ops effort
  • Reduced error potential – single path, reduce brittleness

 

Performance Improvement

  • Getting closer to mobile users
  • Data sources on premises
  • Front ends to the cloud

 

Lifecycle management

  • Moving out of fixed cost infrastructure

What do customers want in hybrid?

  • Run workloads on-premises
  • Run workloads on the cloud
  • Tight integration
  • Without buying new hardware

 

The Challenge of Hybrid

  • Multiple machine formats
  • Incongruent networks
  • Operational inconsistency
  • Skillsets and tooling

The challenge is duplicate effort. <- This should be printed on t-shirts and given out with every conference backpack.

 

VMware Cloud on AWS

 

Account Structure

VMware Cloud SDDC Account

  • A new AWS account created to run a single customer’s SDDC resources
  • Is owned, operated, and paid for directly by VMware
  • Each account is a single tenant for all ESXi hosts

AWS Customer Owned Account

  • Is owned, operated, and paid for directly by the customer
  • Has private connectivity to the VMware Cloud SDDC
  • Has full access to the entire catalogue of native AWS services

 

Topology

Fully configured SDDC running on state of the art infrastructure provisioned on-demand in minutes / hours.

Latest Software

  • VCSA, ESXi, NSX, vSAN, HTML5 Client

Dynamic Capacity

  • DRS / HA Compute Cluster (Intel x86)
  • vSAN Storage Cluster (SSDs)
  • NSX Network Virtualisation (10Gbs+)

Flexible Topology

  • Standalone cloud cluster
  • Hybrid connectivity to on-premises
  • cloud to cloud connectivity

2 different networks – management gateway and compute gateway

 

Connectivity Options

 

Hybrid Use Cases

Consolidate + Migrate

  • DC contract for 12+ months
  • Depreciating assets
  • Long Migration is hybrid

Maintain + Expand

  • Geographic expansion
  • Capacity needs
  • Mainframe

 

Putting It All Together

  • AWS Physical Infrastructure – No dealing with power, cooling, physical security, cross-connects
  • VMware Lifecycle Management – Patching of ESXi, vCenter, NSX, vSAN. Provisioning / deprovisioning
  • Workload flexibility – seamlessly move workloads between on-site and VMware Cloud
  • Elasticity – Scale vSphere clusters up or down based on business demand
  • Cost – convert large capex expenditures to variable expense based on use
  • Expand globally – deploy new DCs through consoles / APIs, not Customs agents
  • AWS Services – 90+ cloud services such as RDS, Amazon Redshfit, S3, and Lambda

Interesting session, I need to dig deeper in terms of tech and business. 3.5 stars.