Not Content: 2018 VMworld...• 3 Converged Infrastructure that were approaching end of lease. • Infrastructure was complex, supporting multiple server and storage platforms. •

VMworld 2018 Content: Not for publication or distribution

©


3Copyright © 2018 Deloitte Development LLC. All rights reserved.

Copyright © 2018 Deloitte Development LLC. All rights reserved.

How Operations Were Simplified

while lowering CapEx and OpExJorvin Martinez, Paul Braren

August 28, 2018













Deloitte migration to vSAN – Agenda

How Operations were simplified while lowering CapEx and OpEx.

Introduction

Hyper-Converged Infrastructure, why vSAN, Total Cost of Ownership

Architecture, creating building blocks to simplify deployments, design options, infrastructure automation.

Migration options, Migration to vSAN, migration demo.

Results , Q & A

Simple. Scalable. Cost-effective.Copyright © 2018 Deloitte Development LLC. All rights reserved.



Jorvin Martinez

Compute Services and Delivery Engineering

@jorvinmartinez

NYC VMUG Co-Leader

Manager, Deloitte Services LP


©2018 VMware, Inc.

Paul BrarenSr. Solution Engineer, HCI/vSAN

Storage and Availability Unit at VMware

@paulbraren

VMUG Presenter / Demo DudeTinkerTry.com virtualization lab

enthusiast


https://twitter.com/paulbraren

https://twitter.com/paulbraren

https://tinkertry.com/




Deloitte migration to vSAN

Why look at Hyper-Converged Infrastructure (HCI).

Server Refresh Drive IT Modernization

Innovate EmpowerEvaluate

Empower Business & IT

• Meet increased customer requirements regarding Agility

• Drive consistent client experiences while providing scalable secure solutions

• Enabling a business-focused approach to IT.

Copyright © 2018 Deloitte Development LLC. All rights reserved.Simple. Scalable. Cost-effective.

• Evaluate emerging technology.

• 3 Converged Infrastructure that

were approaching end of lease.

• Infrastructure was complex, supporting multiple server and storage platforms.

• Consolidate from 11 vCenters to 2 vCenters




Project Phases :

Phase 1

Assessment

• Current State Analysis

• TCO Analysis

• Proof of Concept

Phase 2 Design and Sizing

• Conceptual Design

• Hardware selection

• Physical Design

Phase 3

Implementation

• Build out

• Post implementation Testing

Phase 4

Migration

• Migration Testing

• Migration groups (Phases)

Phase 5

Decommission

• Wipe storage Arrays

• Asset Management

• Return EOL equipment


Project Phases







Evaluation of existing solution.

• Procurement & Provisioning is too slow ( Compute and Storage)

• Infrastructure is too complex

• Gather compute and storage metric

• vROPS or VMware HCI Assessment

• Gather Application requirements (what applications are running in the environment)

Knowledge to support environments required expertise in multiple technologies and platforms: • Storage : VMAX / Multiple VNXs• Compute : HPE / Cisco• Network : Network Switches / Storage

fabric• Virtualization: VMware

• Pleased with infrastructure performance running their critical business application

• MS SQL• Oracle DBs• SAP Sandboxes

• Concerns with capacity as growth pattern is unknown, need to be flexible

Environment Assessment

Customer feedback

Leadership/Management

IT







vSAN Total Cost of Ownership (TCO).

Operational efficiencies include a sizable reduction in:

Capex:• hardware costs (commodity x86 server)• software licensing costs

Opex:• overall power consumption • cooling requirements• staff training cost• fewer staff needed• the number of companies to contact when something goes

wrong

Simplified Annual Total Cost of Ownership







Traditional 3 Tiered Architecture.

TraditionalComplex & Separate Silos

Servers and Blades External Storage Networking Hardware

vSAN Native HCI Architecture

vCenter Management

Resource Efficiency

Expand to Full SDDCvSphere / vSAN







Existing environment diagram.







Why vSAN for HCI

vSphere Virtual SAN

VSAN Datastore

Platform choice (BYO, ReadyNodes, Appliance)

Runs on any standard x86 server

Delivers enterprise-grade scale and performance

Managed through per-VM storage policies

Deeply integrated with the VMware stack







Design Considerations.


Capex:• hardware costs (commodityx86 server)• software licensing costs


wrong

Hybrid or All Flash Networking Solid State Drives Disk GroupsStorage Controllers

• Capacity

• Cache

• Interface speed (SAS/SATA) and impact on redistribution times

• Endurance

• JBOD / pass through mode

• no battery backup required

• high queue depth preferred

• Careful choices supported device, firmware, and driver combination

• Traffic isolation

• 10G v 25G speed and redistribution times

• 1 flash device and 1-7 capacity devices







vSAN Disk Groups

disk group

• Disk groups pool together cache and capacity devices.

• Disk groups are composed of at least 1 flash device and 1-7 capacity devices

• Storage capacity can be provided by either magnetic disks or flash based devices

• Can have 5 disk groups per host = 35 capacity devices per host

• Size affects deduplication

• 2+ Groups per host

disk group disk group disk group disk group

Each host: 5 disk groups max. Each disk group: 1 flash device + 1-7 capacity devices





19

Design Choices

vSAN Storage Policies

- RAID 5 / RAID 6 Erasure Coding is our default

- If performance is the priority, we would modify to a mirror with stripingRAID-5

ESXi Host

parity

data

data

data

ESXi Host

data

parity

data

data

ESXi Host

data

data

parity

data

ESXi Host

data

data

data

parity

ESXi Host

parity

data

data

RAID-6

ESXi Host

parity

data

data

ESXi Host

data

parity

data

ESXi Host

data

parity

data

ESXi Host

data

data

parity

ESXi Host

data

data

parity

RAID-1ESXi Host

data

ESXi Host

data


Presentation title[To edit, click View > Slide Master > Slide Master]


Architecture




21

Environment Diagram - Existing

vC01

VMAXvC02

VNX

vC03

VNX

VNX

vC05

VNX VNX

vC04

VNX VNX

vC06

HP 3PAR

vC07

HP 3PAR

XIV

vC08

HP 3PAR

vC11

IBM

vC09

IBM

vC10

IBM





22

Updated Architecture





23

Updated Architecture

vSphere vSphere / vSANvSphere vSphere / vSANvSpherevSphere/vSAN vSphere/vSAN vSphere/vSAN

Integrated vSAN Storage Storage Array

vSphere vSphere

vCenter (VCSA)








Hypervisor deployment Automation.




wrong


Start PowerShell

Script

Remote Management Config (ILO)

Server Hardware Addition to One view

Server Profile Creation

Server Profile Applied to Hardware

Update Firmware

OS (ESXi) Deployment







Consistent Building Blocks




wrongIntegrated vSAN Storage

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

vSpherevSphere/vSAN

Simplify your deployments. Create clusters as building blocks.

Based on our sizing exercise, We created a standard cluster size of 16 nodes for this project.

Simple. Scalable. Cost-effective.






Performance testing.




wrong



HCIBenchEvaluating performance is an important part of considering any storage solution.


https://labs.vmware.com/flings/hcibench

https://labs.vmware.com/flings/hcibench


Migration






Migration methods




wrong

Migration Option : Downtime required ?

Failback Option

Additional Cost

Backup and Restore Yes Yes Depends (Licensing, HW)

3rd party replication tools Yes Yes Yes

vSphere Replication Yes Yes No

vSphere Replication + SRM Yes Yes Yes

vMotion • XvMotion (Cross Cluster, Cross vCenter)• Cross vCenter Migration Utility Fling

No No*(Backup) No

*Failback from Backup



https://labs.vmware.com/flings/cross-vcenter-workload-migration-utility





Our migration method




wrong


• How much storage ?

• How many VMs did we have to migrate ?

Almost 3,000 VMs

1 PB of data

• What migration method did we ?

Cross vCenter vMotion automated via PowerShell




30

Migration Demo




31

Migration Demo




32

Migration Demo




33

Migration Demo

SATA SATA SATA SATA

FC FC FC FC

STORAGE ARRAY

Disk Group 1

Disk Group 2

Legacy vSAN





34

Migration FYI

• Cross vMotion cannot take place between different version of VDS.

• VMDKs automatically get deleted from the original vCenter if the migrated VM responds to ping.

• Prior to the migration, make sure your set your default vSAN policy.

• Keep an eye on the you vSAN datastore utilization, especially when preparing to kick off hundreds of VM migrations.

• If you are setting you disk to thin, understand how your vSAN policy affects growth. - Mirror vs. Erasure Coding 5/6

vCenter Server places limits on the number of simultaneous virtual machine migration and provisioning operations that can occur on each host, network, and datastore.

Each operation, such as a migration with vMotion or cloning a virtual machine, is assigned a resource cost. Each host, datastore, or network resource, has a maximum cost that it can support at any one time.







Migration FYI




wrong


• Cross vMotion cannot take place between different version of VDS.

• VMDKs automatically get deleted from the original vCenter.

• Prior to the migration, make sure your set your default vSAN policy.• Understand how your policy affects utilization (RAID1, 5, 6)• Understand object space reservation of your storage policy.

• Keep an eye on the you vSAN datastore utilization, especially when preparing to kick off bulk migrations.

• vCenter Server places limits on the number of simultaneous virtual machine migration and provisioning operations that can occur on each host, network, and datastore.






Migration error




wrong


https://kb.vmware.com/s/article/2150316 VMworld 2018 Content: Not for publication or distribution

https://kb.vmware.com/s/article/2150316




Benefits Realized

Cost Optimization:

Capex Savings

• Reduce cost in Hardware

• Reduce cost for Software Licenses.

Consolidated Management

Datacenter footprint :

Current workload went from 18 to 4 Racks, 78 % reduction.

Operations :

Simplified operations

Performance:

Improved performance




38


This publication contains general information only and Deloitte is not, by means of this publication, rendering accounting, business, financial, investment, legal, tax, or other professional advice or services. This publication is not a substitute for such professional advice or services, nor should it be used as a basis for any decision or action that may affect your business. Before making any decision or taking any action that may affect your business, you should consult a qualified professional advisor.

Deloitte shall not be responsible for any loss sustained by any person who relies on this publication.

About Deloitte

Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited, a UK private company limited by guarantee (“DTTL”), its network of member firms, and their related entities. DTTL and each of its member firms are legally separate and independent entities. DTTL (also referred to as “Deloitte Global”) does not provide services to clients. In the United States, Deloitte refers to one or more of the US member firms of DTTL, their related entities that operate using the “Deloitte” name in the United States and their respective affiliates. Certain services may not be available to attest clients under the rules and regulations of public accounting. Please see www.deloitte.com/about to learn more about our global network of member firms.



https://www2.deloitte.com/us/en/legal/about-deloitte.html



Documents

Not Content: 2018 VMworld...• 3 Converged Infrastructure that were approaching end of lease. • Infrastructure was complex, supporting multiple server and storage platforms. •