VMware vSphere 6.0 Knowledge Transfer Kit Architecture Overview

VMware vSphere 6.0Knowledge Transfer KitArchitecture Overview 2015 VMware Inc. All rights reserved.1

AgendaArchitecture OverviewVMware ESXiVirtual machinesVMware vCenter ServerNew Platform Services Controller RecommendationsVMware vSphere vMotionAvailabilityVMware vSphere High AvailabilityVMware vSphere Fault ToleranceVMware vSphere Distributed Resource Scheduler

Content LibraryVMware Certificate Authority (CA)StorageiSCSI Storage ArchitectureNFS Storage ArchitectureFibre Channel ArchitectureOther Storage Architectural ConceptsNetworking22Architecture Overview3VMware vSphere High-Level VMware vSphere Architectural Overview

ESXi

ESXi

ESXi

VMware vCenter ServerManage

Cluster

Physical Resources

ApplicationServicesInfrastructureServicesVMware vSphere vMotionVMware vSphere Storage vMotionVMware vSphere High AvailabilityVMware vSphere FTVMware Data RecoveryDRS and DPMHot AddOver CommitmentContent LibraryvSphere VMFSVMware Virtual VolumesVMware Virtual SANThin ProvisioningVMware vSphere Storage I/O ControlStandard vSwitchDistributed vSwitchVMware NSXVMware vSphere Network I/O ControlAvailabilityScalabilityStorageNetwork4VMware vSphere is the core technology behind any software-defined data center (SDDC).

At the core, the ESXi hosts allow the physical networking, storage, and compute (memory and CPU) resources to be managed in such a way that multiple virtual machines can be run simultaneously on the same physical host and resources.

This not only allows for them to avoid idle servers, but it allows for a reduction of data center footprint as a result. vCenter Server can manage multiple ESXi hosts, and in doing so, enables many features that are not available if only using a single server. Using vCenter Clusters, host resources can be aggregated to allow for better availability and utilization of resources. In addition to this, it enables features such as vSphere High Availability, DRS, and vSphere vMotion as well as many of the other services listed on the slide.4How Does This Fit With the Software-Defined Data Center (SDDC)?TEXT

Self-Service App DevelopmentApp BlueprintingApp Deployment StandardizationCloud App PublishingSelf-Service User PortalCatalogs and Standard TemplatesLow Admin OverheadCore VirtualizationMonitoring with Performance and CapacityOrchestration with Workflow LibraryVirtualization of Physical AssetsSoftware-Defined NetworkingApplication ServiceInfrastructure ServiceSDDC Foundation

Cloud Ready

Compliance

BCDR

HybridCloud

SDS

SDN

FinancialVMwareVirtual SANVMware NSXSRMVRvDPAVMware vRealize BusinessvRealize Operations ManagervSphere Infrastructure NavigatorvRealize OrchestratorHyperic

vRealize Log InsightVMware vRealize Application ServicesVMware vSphereVMware vRealize AutomationvRealize Config. ManagerVMware vCloud Connector5Layer 1: SDDC Foundation this layer represents the core technical elements that make up a properly populated software-defined data center ready for today and tomorrow.

At the most basic level of this service, everyone who adopts this approach gets this layer. Its the default. We use the term foundation often and intentionally, to signify that the journey to SDDC is not complete for VMware and that new technologies and architectures that challenge this model will come.

The products encompassed at this level are:

vSphere (ESXi, vCenter Server)vCenter Network Services (VMware vShield Manager)VMware vRealize OrchestratorVMware vRealize Operations Manager VMware vRealize HypericVMware vRealize Log Insight

Layer 2: Infrastructure Service this layer represents establishing a cloud computing metaphor on top of the core technologies represented by SDDC Foundation. A self-service access model, through an end-user portal with catalog-based consumption and standardized templates is established here. This layer is commonly associated with vRealize Automation and was previously associated with VMware vCloud Director.

Layer 3: Application Service this layer represents a maturity beyond provisioning VMs and OS instances, towards a model equipped to allow for multitier application development with an emphasis on the application, not the VM. This is commonly associated with VMware vCloud Application Director.

The modules: These elements represent technologies in the VMware portfolio that commonly add to, or enhance, the core functionality found in SDDC Foundation. They are considered out of scope for the core technology elements of SDDC Foundation, but they are accounted for in the core design, such that a completely new architecture is not required to add them. The modules are:

SDS Software-Defined Storage is the VMware Virtual SAN technology framework.

NextGen Network NSX-v is the next generation of vCloud Networking and Security.

Compliance Represents vRealize Configuration Manager and the related compliance discipline.

BCDR Represents both disaster recovery technologies (VMware vCenter Site Recovery Manager and VMware vSphere Replication) and backup/recovery technologies (VMware vSphere Data Protection and VMware vSphere Data Protection Advanced)

Hybrid Cloud VMware vCloud Connector.

Cost Management vRealize Business Standard and related costing efforts.

5VMware ESXi6ESXi 6.0ESXi is bare metal VMware vSphere HypervisorESXi installs directly onto the physical server enabling direct access to all server resourcesESXi is in control of all CPU, memory, network and storage resourcesAllows for virtual machines to be run at near native performance, unlike hosted hypervisorsESXi 6.0 allows Utilization of up to 480 physical CPUs per hostUtilization of up to 12 TB of RAM per hostDeployment of up to 2048 virtual machines per host7

VMware ESXi

7ESXi Architecture

VMware Management FrameworkVMware Management FrameworkVMware Management FrameworkCommonInformation Model (CIM)Agentless Hardware MonitoringAgentless Systems ManagementCLI Commandsfor Configurationand SupportVMkernelESXi Host

Network and StorageLocal Support Console (ESXi Shell)88Virtual Machines9Virtual MachinesThe software computer and consumer of resources that ESXi is in charge ofVMs are containers that can run any almost any operating system and application.Segregated environment which does not cross boundaries unless via network or otherwise permitted through SDK accessEach VM has access to its own resourcesVMs generally do not realize that they are virtualized10ESXi Host Virtual MachineAppAppAppOperating System

CPU

RAM

Disk

Network / Video Cards

CD / DVD

SCSI Controller

Mouse

KeyboardA virtual machine is a software computer which, like a physical computer, runs an operating system and applications. The virtual machine consists of a set of specification and configuration files and is backed by the physical resources of a host. Every virtual machine has virtual devices that provide the same functionality as physical hardware are more portable, more secure, and easier to manage.

A virtual machine consists of several files that are stored on a storage device. The key files are the configuration file, virtual disk file, NVRAM setting file, and log file. You configure virtual machine settings through the VMware vSphere Web Client, one of the vSphere command-line interfaces (VMware vSphere PowerCLI, vCLI) or the VMware vSphere Web Services SDK.10Virtual Machine ArchitectureVirtual machines consist of files stored on a vSphere VMFS or NFS datastoreConfiguration file (.vmx)Swap files (.vswp)BIOS files (.nvram)Log files (.log)Template file(.vmtx)Raw device map file (-rdm.vmdk)Disk descriptor file (.vmdk)Disk data file (VM_name>-flat.vmdk)Suspend state file (.vmss)Snapshot data file (.vmsd)Snapshot state file (.vmsn)Snapshot disk file (-delta.vmdk)11Except for the log files, the name of each file starts with the virtual machines name (). A virtual machine consists of the following files:

A configuration file (.vmx).

One or more virtual disk files. The first virtual disk has files .vmdk and -flat.vmdk.

A file containing the virtual machines BIOS settings (.nvram).

A virtual machines current log file (.log) and a set of files used to archive old log entries (-#.log).

Swap files (.vswp) are used to reclaim memory during periods of contention.

A snapshot description file (.vmsd). This file is empty if the virtual machine has no snapshots.

If the virtual machine is converted to a template, a virtual machine template configuration file (.vmtx) replaces the virtual machine configuration file (.vmx).

If the virtual machine has more than one disk file, the file pair for the second disk file and later is named _#.vmdk and _#-flat.vmdk. Where # is the next number in the sequence, starting with 1. For example, if the virtual machine named Test01 has two virtual disks, this virtual machine has the files Test01.vmdk, Test01-flat.vmdk, Test01_1.vmdk, and Test01_1-flat.vmdk.

In addition to the current log file, vmware.log, up to six archive log files are maintained at one time. For example, -1.log to -6.log might exist at first. The next time an archive log file is created (for example, when the virtual machine is powered off and powered back on), the following occurs. -2.log to -7.log are maintained (-1.log is deleted), then -3.log to -8.log, and so on.

A virtual machine can have other files. For example, if one or more snapshots were taken or if raw device mappings (RDMs) were added. A virtual machine has an additional lock file if it resides on an NFS datastore. A virtual machine has a change block tracking file (.ctk) if it is backed up with the vSphere Data Protection appliance or other backup software that has enabled the CDP feature.11VMware vCenter Server12

VMware vCenter 6.0 vCenter is the management platform for vSphere environmentsProvides much of the feature set that comes with vSphere, such as vSphere High Availability Also provides SDK access into the environment for solutions such as VMware vRealize AutomationvCenter Server is available in two flavorsvCenter for WindowsvCenter Server ApplianceIn vSphere 6.0, both versions offer feature parityA single vCenter Server 6.0 can manage1000 hosts10,000 virtual machines1313vCenter 6.0 ArchitectureIn vCenter 6.0, the architecture has changed dramatically Provided by Platform Services ControllersVMware vCenter Single Sign-OnLicense serviceLookup serviceVMware Directory ServicesVMware Certificate AuthorityProvided by vCenter Server ServicevCenter ServerVMware vSphere Web Client Inventory ServiceVMware vSphere Auto Deploy VMware vSphere ESXi Dump CollectorvSphere Syslog Collector on Windows and vSphere Syslog Service for VMware vCenter Server Appliance

14All services are provided from either a Platform Services Controller or vCenter Server instance

14vCenter 6.0 Architecture (cont.)Two basic architectures are supported as a result of this changePlatform Services Controller is either Embedded or External to vCenter ServerChoosing a mode depends on the size and feature requirements for the environment 15

Embedded Platform Services Controller

External Platform Services Controller15vCenter 6.0 Architecture (cont.)Enhanced Linked Mode is a major feature that impacts the architectureWhen using Enhanced Linked Mode it is recommended to use an external Platform Service ControllerFor details about architectures that VMware recommends and the Implications of using them, see VMware KB article, List of Recommended topologies for vSphere 6.0 (2108548 (http://kb.vmware.com/kb/2108548)

16These architectures are Recommended

Enhanced Linked Mode (No High Availability)Enhanced Linked Mode (With High Availability)

16vCenter 6.0 Architectures (cont.)17These architectures are Not Recommended

Enhanced Linked Mode (Embedded PSCs)

Enhanced Linked Mode (Embedded PSC with External vCenter)Enhanced Linked Mode (Embedded PSC linked with External PSC)17vCenter 6.0 Architecture (cont.)Enhanced Linked Mode has the following maximumsThe architecture should also adhere to these maximums to be supported

18DescriptionScalability MaximumNumber of Platform Services Controllers per domain8Maximum Platform Services Controllers per vSphere site (behind a single load balancer)4Maximum objects in a vSphere domain (users, groups, solution users)1,000,000Maximum number of VMware solutions connected to a single Platform Services Controller4Maximum number of VMware products/solutions per vSphere domain1018vCenter Architecture vCenter Server ComponentsDatabaseServerPlatform Services Controller (IncludingvCenter Single Sign-On)VMware vSphere APIUserAccessControlESXi ManagementCore and Distributed ServicesAdditional Services: VMware vSphere Update Manager vRealize OrchestratorvSphere Web ClientVMware vSphere ClientThird-PartyApplicationsPlug-InsvCenter Server Database

ESXi hosts

Microsoft Active Directory Domain

1919vCenter Server consists of the following services and interfaces:

Core services include management of resources and virtual machines by the Inventory service, task scheduling, statistics logging, management of alarms and events, virtual machine provisioning, and host and virtual machine configuration.

The vCenter Lookup Service contains topology information about the vSphere infrastructure, enabling vSphere components to connect to each other securely. Services, such as the Inventory service and vCenter Server, register with the vCenter Lookup service so that other vSphere components, like the vSphere Web Client, can find them.

Distributed services including vSphere vMotion, DRS, and vSphere High Availability, which are installed with vCenter Server.

Additional services are packaged separately from the base product and requires separate installation. No additional license is necessary. Examples include VMware vSphere Update Manager and VMware vRealize Orchestrator.

Database interface provides access to the vCenter Server database.

vCenter Server provides access to the ESXi host through a vCenter Server agent, which is started on the host when it is added to the vCenter Server inventory.vCenter Architecture ESXi and vCenter Server Communication20How vCenter Server components and ESXi hosts communicatevCenter Server& Platform Services Controller

ESXi Hosthostdvpxa

vpxdTCP/UDP 902TCP/UDP 902TCP 443TCP443, 944320VMware vSphere vMotion21vSphere vMotionvSphere vMotion allows for live migration of virtual machines between compatible ESXi hostsCompatibility determined by CPU, network, and storage access With vSphere 6.0, migrations can occurBetween clustersBetween datastoresBetween networks Between vCenter Servers Over long distances as long as RTT is