Scribd Logo
Upload

Welcome to Scribd!

  • GCVE - GCE Comparison

    Uploaded by

    PS Manikandan
    449 views9 pages
    This document discusses strategies for modernizing applications using Google Cloud VMware Engine (GCVE) or Google Compute Engine (GCE). It outlines two main strategies - Lift and Shift and Lift and Optimize. Lift and Shift involves migrating VMs from an on-premises VMware environment to GCVE with no changes, while Lift and Optimize migrates workloads to GCE and transforms them to be optimized for the cloud. The document then compares the pros and cons of each approach and outlines why GCVE may be preferable to similar offerings from AWS or Azure.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document discusses strategies for modernizing applications using Google Cloud VMware Engine (GCVE) or Google Compute Engine (GCE). It outlines two main strategies - Lift and Shift and Lift and Optimize. Lift and Shift involves migrating VMs from an on-premises VMware environment to GCVE with no changes, while Lift and Optimize migrates workloads to GCE and transforms them to be optimized for the cloud. The document then compares the pros and cons of each approach and outlines why GCVE may be preferable to similar offerings from AWS or Azure.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    449 views9 pages

    GCVE - GCE Comparison

    Uploaded by

    PS Manikandan
    This document discusses strategies for modernizing applications using Google Cloud VMware Engine (GCVE) or Google Compute Engine (GCE). It outlines two main strategies - Lift and Shift and Lift and Optimize. Lift and Shift involves migrating VMs from an on-premises VMware environment to GCVE with no changes, while Lift and Optimize migrates workloads to GCE and transforms them to be optimized for the cloud. The document then compares the pros and cons of each approach and outlines why GCVE may be preferable to similar offerings from AWS or Azure.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 9

    Shift (GCVE)

    Lift &
    Optimize (GCE)

    RR – Feb 2021
    Decision Tree -
    Application
    Modernization
    Re-platform
    Cloud
    Migrate GCE
    Rehost -
    Migration
    using HCX
    GCVE
    GCVE GCE

    Lift & Shift


    • Lift & Shift – Closest to source • Lift & Optimize – Closer to modernization
    • Vmware to Vmware • Any source to GCE
    Vs • Uses HCX to migrate VMs • Uses Cloud Migrate (Velostrata) to
    migrate to GCE
    Lift & Optimize • Fixed Compute nodes
    • Maintains homogeneity between source
    • Elastic compute nodes
    and destination • Transforms and optimizes on the fly
    • Consistent Behaviour • Replatform could result in rollbacks
    • No changes to boot • Faster boot
    • Vmotion requires ESXi 5.5 minimum • Depends on source
    • Direct Interconnect is needed • Direct Interconnect preferred
    • Uses NSX-T for VMWare Management • VPC
    and VPC for VMs
    • Flexible Cost/ use and throw
    • Fixed Cost based on allocation with
    minimum 3 node purchase (expensive) • Google VMs
    • To reduce TCO, may consider GCE as next • To modernize, may consider GKE as next
    phase phase
    Google Cloud VMware AWS and Azure
    Impact
    Engine Environments

    Cost Savings ✓ GCVE 25%+ cheaper than On ✕ More expensive than Google
    Prem Cloud

    Consumption Model ✓ First party service, unified ✕ Fragmented by partnership


    connectivity models

    Why Google Connectivity ✓ Enterprise grade redundancy


    and reliability in Google Cloud
    ✕ AWS non-redundant
    ✕ Neither AWS nor Azure able to

    Cloud ✓ Leverage Google Cloud native


    network services
    consume native Cloud network
    services

    Vmware Single Relationship ✓ One stop-shop - purchase, ✕ Multiple contracts with VMC and

    Engine support, VMware licenses, and


    Cloud - with no other vendors
    involved
    AWS
    ✕ Azure VMware solution is a non-
    native marketplace solution

    Application Modernization ✓ Segue to app mod at ✕ Limited by non-native, multi-party


    customer’s own pace enabled complexity
    by above attributes
    GCVE over On-prem

    Ease migration Lower costs Run securely Create Innovate


    operational agility
    Move VMware workloads Deliver efficiency Run with confidence Operational continuity Build on Google Cloud services
    to the cloud as-is
    Leverage Google Provide best in class Unified management
    Cloud SQL Tensorflow
    No refactoring Cloud economies security
    of scale Cloud Operations
    Maintain continuity Anthos
    Google
    Kubernetes Network
    Engine

    BigQuery Cloud
    Storage

    Migrate Run Innovate


    Backup of VMware VMs - Example using Veeam

    Google Cloud VMware Engine

    Dedicated VMware Stack


    Google Cloud
    Customer VPC

    Proxy Veeam Backup


    Repository
    Cloud
    Storage

    You might also like