La virtualisation - VMware

Présentation au sujet: "La virtualisation - VMware"— Transcription de la présentation:

1 La virtualisation - VMware
Jeudi 4 Juin 2009 La virtualisation - VMware 1

2 Pourquoi la virtualisation ?
Prédominance de serveurs x86 en entreprises : 91% des serveurs d’entreprise acquis en 2004 (Gartner Dataquest) Prolifération des serveurs : • 1 système d’exploitation ou application par serveur Sous utilisation des ressources serveurs : Taux d’utilisation d’un serveur x86 relevé de 5 à 15% Les avantages de la virtualisation évolues : Taux de consolidation Souplesse d’administration Disponibilité– PCA/PRA Rendre l’informatique aussi simple que le réseau électrique

3 Vos défis Diminution du TCO Sécurité Réactivité
Prolifération des serveurs Utilisation des ressources Sécurité Sécurisation des serveurs Protection contre les sinistres. Sauvegardes & restaurations. Réactivité Diminution des cycles de mise en œuvre.

4 Les principes de la virtualisation : La consolidation
Infrastructure virtualisée Infrastructure traditionnelle Déploiement de plusieurs machines virtuelles sur un même serveur physique Machines virtuelles Couche de vitualisation Augmentation du taux d’utilisation Serveur physique Les limitation des architectures physiques : Une machine physique est limitée par un OS et certaines incompatibilité d’applications: Relation de dépendance entre le matériel et l’OS créée pendant chacune des installations Baisse du TCO

5 Anatomie d’une machine virtuelle
Chaque machine virtuelle est un système complet encapsulé dans un ensemble de fichiers Application non modifiée OS non modifié Matériel virtuel Application Système d’exploitation Carte réseau HBA Disque CPU Machines virtuelles Couche de virtualisation Serveur physique

6 Les plateformes de virtualisation
Management - Optimisation – Continuité Plateformes de virtualisation VMware ESX Server 4 VMware ESX Server 4i VMware VMFS VMware Virtual SMP VMware Server VMware Workstation VMware Fusion VMware Player hyperviseur Host-based

7 ESX Server : Le standard de la virtualisation
Ajout suppression à chaud CPU/RAM/périphériques 10 x Gigabit Ethernet 255 Go de RAM 8 CPU virtuels Jusqu’à 256 VMs démarrées simulanément SAN Fibre Channel SAN iSCSI NAS (NFS) DAS SCSI & SATA Volumes jusqu’à 64 To Boot from SAN 32 NICs 10 GigE Infiniband NIC Teaming VLAN Tagging 64 Coeurs 1 To

8 ESX Server : Optimisation des ressources
Memory overcommitment Mémoire VM > Mémoire physique Memory page sharing Optimisation du stockage des pages mémoire Allocation dynamique de ressources Augmenter ou diminuer les ressources allouées aux Machines virtuelles à chaud

9 ESX Server : Quels OS supportés ?
Serveurs Microsoft Desktop Microsoft Linux Autres Support experimental Windows 3.1 Windows 95 Windows 98 Asianux CentOS Debian FreeBSD Ms-Dos 6 OS/2 OpenServer UnixWare

10 Gestion des ressources – Disponibilité – Mobilité – Sécurité
La disponibilité Infrastructure Virtuelle VMware VMotion – storage VMotion VMware HA - FT VMware Consolidation Backup VMware DRS VMware Update Manager Gestion des ressources – Disponibilité – Mobilité – Sécurité

11 VMotion : Migration à chaud de machines virtuelles
50 % des clients VMware ont mis en œuvre VMotion Intervention & Upgrade sur le matériel sans interruption de service Remplacement de serveurs sans interruption de service Fiabilité reconnue / 6 ans d’expérience

12 Besoin d’une intervention matérielle
VMotion : Exemple d’utilisation Besoin d’une intervention matérielle File Server AD Controller Web Server Oracle Server 1. VMotion 2. Upgrade mémoire DNS / DHCP SQL Server 3. VMotion ESX Server A ESX Server B ESX Server C

13 Distributed Resource Scheduler
VMware DRS : Répartition de charge Distributed Resource Scheduler File Server Intranet Server AD Controller Web Server Oracle2 Server Oracle Server DNS / DHCP SQL Server SQL2 Server Nouveau Serveur ESX ESX Server A ESX Server B ESX Server C

14 Distributed Power Management
VMware DPM : Economies d’énergie Distributed Power Management Oracle2 Server File Server AD Controller Intranet Server Web Server Oracle Server SQL2 Server DNS / DHCP SQL Server ESX Server A ESX Server B ESX Server C ESX Server D

15 Haute disponibilité : VM HA Failure
High Availability Oracle2 Server File Server AD Controller Intranet Server Web Server Oracle Server SQL2 Server DNS / DHCP SQL2 Server SQL Server ESX Server A ESX Server B ESX Server C ESX Server D

16 Haute disponibilité : VMware HA
High Availability Oracle2 Server File Server Oracle2 Server AD Controller Intranet Server Intranet Server Web Server Oracle Server DNS / DHCP SQL2 Server SQL Server ESX Server A ESX Server B ESX Server C ESX Server D

17 Haute disponibilité – Fault Tolerance
VMware ESX – FT Haute disponibilité – Fault Tolerance Serveur WEB Serveur WEB Serveur WEB ESX Server A ESX Server B ESX Server C Réplication RAM Réplication RAM

18

19 vStorage Thin Provisionning
vStorage Thin Provisionning OS APPL. OS APPL. OS APPL. Les disques de la machine virtuelle ne consomment que la quantité d’espace physique utilisée La machine virtuelle détecte en permanence la taille totale du disque logique Alertes et états complets sur l’allocation et la consommation Nette amélioration du taux d’utilisation du stockage Plus besoin de surprovisionner les disques virtuels Jusqu’à 50 % de réduction des coûts de stockage VMware ESX Standard (thick) Fin (thin) Fin (thin) 20 Go 40 Go 100 Go Disques virtuels 20 Go 20 Go 40 Go 100 Go Banque de données Storage Thin Provisioning optimise les coûts du stockage grâce à une utilisation efficace de ce dernier dans les environnements virtuels. Les utilisateurs surestiment bien souvent leurs demandes de stockage afin de ne pas réitérer trop souvent le processus de demande/approbation. Avec vStorage Thin Provisioning, le département informatique peut désormais fournir aux utilisateurs de l’entreprise l’espace de stockage dont ils ont réellement besoin et n’en racheter que lorsque que cela s’avère vraiment nécessaire. Des alertes et états complets sur l’allocation et la consommation permettent de s’assurer que les machines virtuelles ne manquent pas d’espace de stockage. Storage vMotion et Volume Grow (diapositive suivante) veillent, quant à eux, à ce que les machines virtuelles puissent migrer vers des banques de données contenant de l’espace supplémentaire ou bien que la taille des volumes puisse être augmentée lorsque la quantité d’espace consommée se rapproche de la quantité allouée. 60 Go 20 Go

20 VMware Update Manager – Mises à jour automatisées
Automatisation des mises à jour ESX Automatisation des mises à jour des VMs Patches Windows OFFLINE Patches RedHat Retour arrière possible (Snapshot) Update Manager ESX Server

21 Stockage sur disque avec dé-duplication
VMware Data Recovery Sauvegarde et récupération sur disque de vos machines virtuelles sans l’aide d’agent Restauration au niveau VM ou fichier Sauvegardes incrémentielles et dé-duplication pour économiser de l’espace disque Protection des données rapide, simple et complète pour vos VM Gestion centralisée par vCenter Gestion économique du stockage X OS APPL. OS APPL. OS APPL. VMware ESX vCenter Data Recovery est un nouvel outil mis à disposition des utilisateurs de VMware vSphere™ afin d’assurer la protection intégrale des données de leurs machines virtuelles. Vous noterez qu’il convient à des environnements de petite taille (100 VM ou moins). - Il s’agit d’une solution de sauvegarde et de restauration sur disque, conviviale et rapide. - Elle est bâtie sur l’API VCB et s’intègre pleinement avec la gestion de vCenter pour permettre une planification centralisée et efficace des tâches de sauvegarde à l’aide d’un workflow intuitif. Stockage sur disque avec dé-duplication

22 VMware Data Recovery Outil de sauvegarde/restauration Vmware
Sauvegarde et restauration sur disque sans déploiement d’agent dans les VMs De-duplication et sauvegarde incrémentielle afin de réduire l’espace disque

23 Souplesse d’administration
Management - Optimisation – Continuité  Management & Automatisation VMware VirtualCenter VMware Converter VMware Capacity planner VMware Site recovery Manager VMware View VMware Lab Manager

24 VirtualCenter - Principales fonctions
Gestion des machines virtuelles et des serveurs 1 7 Interfaces de programmation Provisionnement 2 Gestion centralisée Sécurité et contrôle d’accès 6 Migration 3 Surveillance des systèmes 5 Administration des ressources 4

25 Site Disaster Recovery VMware Infrastructure VMware Infrastructure
VMware Site Recovery Manager - PRA Site de Production Site Disaster Recovery VirtualCenter Site Recovery Manager Site Recovery Manager Site Recovery Manager VirtualCenter Virtual Machines Virtual Machines Machines virtuelles protégées VMware Infrastructure VMware Infrastructure Servers Servers Key Points: Site Recovery Manager requires a running VirtualCenter management server instance and a running Site Recovery Manager service instance on each site Site Recovery Manager also requires that third-party storage-based replication (also known as array-based replication) be installed and configured Script: Site Recovery Manager will require that a customer have access to a recovery site (in some cases it could be a hosted or co-location site). At the recovery site, the customer will need to have: A separate VirtualCenter management server up and running Site Recovery Manager installed The minimum number of ESX Server hosts needed to provide sufficient resources for recovery Storage that is used as the target for the replication software Site Recovery Manager operates on paired sites, e.g. one site protects another. For each pair of sites that are protected, the above requirements apply. Additional requirements: Applications being protected must be able to tolerate active/passive failure VMFS is used for all replicated virtual machines (RDMs are only supported experimentally in 1.0) In order to communicate with storage replication, storage replication credentials must be provided to the VirtualCenter management server Storage Replication gérée par la baie SAN Storage

26 Nouveautés de vSphere 4.0 : présentation technique
Alexandre HUGLA Specialist Systems Engineer VMware France

27 Concept cloud computing
Services d’applications Concept cloud computing .Net Windows Linux J2EE Grid Web 2.0 SaaS vApp Services d’infrastructure Suite vCenter Disponibilité Sécurité Évolutivité vMotion Storage vMotion HA Fault Tolerance Data Recovery vShield Zones VMSafe DRS Ajout à chaud VMware vSphere™ 4.0 vCompute vStorage vNetwork VMware ESX VMware ESXi DRS/DPM VMFS Thin Provisioning VMFS Volume Grow Distributed Switch This is the summary diagram of vSphere and its components Cloud interne Cloud externe *Remarque : vCenter Server et ses composants sont vendus séparément

28 Affectation de ressources planifiée
vCompute vStorage vNetwork Home > Management > Scheduled Tasks > Add vCenter4 includes a new scheduled task to change the resource settings of a resource pool or virtual machine. You can configure the task to change the shares, reservation, and limit for CPU, Memory, or both so that you can accommodate business priorities that change throughout the year. For example, at the end of each quarter you could give financial applications higher priority than internal applications. Or, if you were a retail organization, you could double the resource reservations for the online store virtual machines during the month of December. Afin de suivre l’évolution des priorités métier, planifiez des tâches pour modifier les paramètres de ressources.

29 Multipathing vmware (PSA)
vCompute vStorage vNetwork Les SATP (Storage Array Type Plugins) gèrent le basculement de chemin, surveillent le bon fonctionnement des chemins et signalent les changements au NMP. Les PSP (Path Selection Plugins) choisissent le meilleur chemin. SATP PSP Pile de stockage VMkernel NMP PSA The VMkernel storage stack has been restructured to include a modular Pluggable Storage Architecture (or PSA) that provides superior multipathing support. The PSA coordinates the operation of both a Native Multipathing Module and custom software plugin modules developed using the vStorage APIs for Multipathing. VMware provides a default multipathing module with ESX called the Native Multipathing Module (or NMP). The NMP associates a set of physical paths with a specific storage device, or LUN. The NMP supports all storage arrays listed on the VMware storage hardware compatibility list and provides a path selection algorithm based on the array type. The NMP has two sub-plugins for failover and load balancing: Storage Array Type Plugins (known as SATPs) and Path Selection Plugins (know as PSPs). Storage Array Type Plugins handle path failover for a given storage array. SATPs run in conjunction with the NMP and are responsible for array‐specific operations. ESX offers an SATP for every type of array that VMware supports, generic SATPs for non‐specified storage arrays, and a local SATP for direct‐attached storage. Each SATP accommodates special characteristics of a certain class of storage arrays and can perform the array‐specific operations required to detect path state and to activate an inactive path. As a result, the NMP module can work with multiple storage arrays without having to be aware of the storage device specifics. After the NMP determines which SATP to call for a specific storage array and associates the SATP with physical paths from the storage array, the SATP monitors health of each physical path and reports changes in the state of each physical path to the NMP. The SATP also performs array‐specific actions necessary for storage fail‐over. For example, for active/passive devices, it can activate passive paths. Path Selection Plugins run in conjunction with the NMP and are responsible for choosing the physical path for I/O requests. The NMP assigns a default PSP for every logical device based on the SATP associated with the physical paths for that device. You can override the default PSP. The NMP supports the following PSPs: Most Recently Used selects the path it used most recently. If this path becomes unavailable, the ESX host switches to an alternative path and continues to use the new path while it is available. Fixed uses the designated preferred path, if it has be configured. Otherwise, it uses the first working path discovered at system boot time. If the ESX host cannot use the preferred path, it selects a random alternative available path. The ESX host automatically reverts back to the preferred path as soon as the path becomes available. And Round Robin uses an automatic path selection rotating through all available paths and enabling load balancing across the paths. HBA 1 HBA 2

30 vStorage Thin Provisioning
vCompute vStorage vNetwork Disques virtuels 40 Go 20 Go 120 Go alloués 20 Go 20 Go Standard (thick) 40 Go Fin (thin) 80 Go Fin (thin) Banque de données When you create a virtual machine, a certain amount of storage space on a datastore is provisioned, or allocated, to your virtual disk files. By default, vSphere offers a traditional storage provisioning method by which you estimate in advance how much storage a virtual machine will need for its entire lifecycle, provision a fixed amount of storage space to its virtual disk, and have the entire provisioned space committed to the virtual disk during its creation. This type of virtual disk that immediately occupies the entire provisioned space is called a thick disk. Creating virtual disks in thick format can lead to underutilization of datastore capacity because large amounts of storage space, pre‐allocated to individual virtual machines, might remain unused. For example, say you have a 500 GB volume allocated to an application with only 100 GB of actual data, the other 400 GB has no data stored on it. That unused capacity is still dedicated to that application and no other application can use it. This means that the unused 400 GB is wasted storage, which means that it is also wasted money. And even though all of the storage capacity may eventually be used, it could take years to do so. To avoid over allocating storage space and minimize stranded storage, vSphere 4 supports storage over-commitment in the form of thin-provisioning virtual disks. When a disk is thin-provisioned, the virtual machine thinks it has access to a large amount of storage, but the actual physical footprint is much smaller. Disks in thin format look just like disks in thick format in terms of logical size, but the VMFS version 3 driver manages them differently in terms of physical size. The VMFS 3 driver allocates physical space for thin-provisioned disks on first write and expands the disk on-demand if and when the guest operating system needs it. This capability allows you to allocate the total provisioned space for disks on a datastore at a greater amount than the actual capacity. If the VMFS volume is full, and a thin disk needs to allocate more space for itself, the virtual machine prompts you to provide more space on the underlying VMFS datastore. vSphere also provides alarms and reports that specifically track allocation versus current usage of storage capacity so you can optimize the allocation of storage for you virtual environment. Capacité de 100 Go 80 Go utilisés 60 Go 20 Go

31 Opérations de provisionnement fin de disques
vCompute vStorage vNetwork Une option de disque au format fin est disponible lorsque vous : Créez une machine virtuelle Clonez vers un modèle Clonez une machine virtuelle Faites migrer l’espace de stockage de machine virtuelle (Storage vMotion) Assistant de création de machines virtuelles You can choose to deploy a thin provisioned disk when you: Create a virtual machine Clone to a template Clone a virtual machine And migrate virtual machines Thin disks require VMFS-3 and newer datastores, so if the selected datastore is an earlier version, vSphere will create the disk in thick format. Assistants de clonage et de migration de machines virtuelles

32 Option VMFS Volume Grow
Ajout d’extension Volume Grow Volume Grow utilise une extension de façon à remplir la capacité adjacente disponible. Une partition unique assure une meilleure disponibilité de la machine virtuelle Peut augmenter un volume plusieurs fois jusqu’à la taille d’un volume VMFS Il faut d’abord augmenter la LUN associée à la banque de données VMFS Effectuer l’extension immédiatement après nécessite de l’espace libre dans l’unité logique vSphere 4 adds a new option to dynamically increase the capacity of a running VMFS datastore when virtual machines require more space. Rather than adding a second extent, you can grow an existing extent so that it fills the available adjacent capacity without disrupting running virtual machines. The newly available space appears as a larger VMFS volume along with an associated grow event in vCenter. Before growing a VMFS volume, you must use an array management utility to grow the LUN backing the datastore. Only extents with free space immediately after them are expandable.

33 API vStorage de protection des données
Application de sauvegarde Serveur physique ou VM (Windows ou Linux) API vStorage de protection des données Data Mover centralisé Serveur proxy de sauvegarde Montage vSphere 4 introduces a new set of APIs to replace the existing backup framework previously provided by VMware Consolidated Backup (VCB). The vStorage APIs for Data Protection allow VMware partners to develop virtual machine backup applications that integrate seamlessly with vSphere 4 and later. Although VCB will continue to be provided and supported with vSphere 4, new features will only be available via these APIs and VCB will eventually be retired in the future. This diagram shows the backup architecture using vStorage APIs for Data Protection. Notice that the VMware Consolidated Backup software is no longer a component of the architecture. Instead, backup application developers integrate the VCB functionality directly into the backup application via the vStorage APIs for Data Protection. That means the backup application is a complete solution, designed specifically to back up virtual machines in a vSphere datacenter. Backup software partners have indicated strong support for the vStorage APIs for Data Protection. Among the partners planning to update their products in 2009 to support these APIs: CA (ArcServe) Commvault (Galaxy Simpana) EMC (Avamar, Networker) HP (Data Protector) IBM (Tivoli Storage Manager) Symantec (Backup Exec, Backup Exec System Recovery, NetBackup Enterprise) Vizioncore (vRanger Pro) Snapshots Stockage SAN

34 Couche de virtualisation
E/S VMDirectPath Le pilote du périphérique d’E/S accède directement au périphérique physique Prise en charge complète du réseau avec : Contrôleur 10 Gigabit Ethernet Intel 82598 Adaptateur réseau 10 Gigabit Broadcom 57710 Prise en charge expérimentale de périphériques d’E/S de stockage avec : Fibre Channel 8 Gbits/s QLogic QLA25xx Adaptateurs SAS 3 Gbits/s LSI 3442e-R et 3801e (basés sur processeur 1068) Les machines virtuelles doivent être exécutées sur une plate-forme Intel Nehalem Chaque machine virtuelle peut se connecter à deux périphériques passthrough au maximum. Accroît les performances, mais au prix de la perte de plusieurs fonctions de virtualisation vMotion, ajout/retrait à chaud de périphériques virtuels, interrompre et reprendre, enregistrement et lecture, Fault Tolerance, High Availability, surdimensionnement de la mémoire et partage de pages MMU d’E/S Périphérique d’E/S Couche de virtualisation VMDirectPath is a new ESX 4 feature that allows device drivers in virtual machines to bypass the virtualization layer so that they can directly access and control a physical device. VMDirectPath I/O provides this capability to I/O device drivers. VMDirectPath I/O relies on DMA Address Translation in an I/O Memory Management Unit to convert guest physical addresses to host physical addresses. ESX 4 fully supports this first generation of VMDirectPath I/O with the Intel Gigabit Ethernet Controller and provides experimental support for storage I/O devices with the QLogic QLA25xx 8Gb Fibre Channel and the LSI 3442e-R and 3801e (1068 chip based) 3Gb SAS adapters. Support is limited to Intel and AMD CPUs with EPT/NPT/RVI support. VMDirectPath I/O device access is primarily targeted to those applications that can benefit from direct access by the guest operating system to the I/O devices. Other virtualization features, such as VMotion, hardware independence, and sharing of physical I/O devices is not yet available to virtual machines using this feature. However, VMware is planning to extend the hardware support and virtualization features in the next generation of DirectPath I/O.

35 Architecture de switch standard
Configuration réseau au niveau de l’hôte Console de service Cartes réseau virtuelles Groupes de ports Port vMotion Groupes de ports de VM Port vMotion Groupes de ports de VM Port COS vSwitchs vNetwork components build on the VI3 networking infrastructure, so let’s quickly review that architecture. VI3 network configuration is done at the host level. Each virtual machine and the service console has one or more of its own virtual network adapters, or vNICs. The operating system and applications talk to a vNIC through a standard device driver or a VMware optimized device driver. The VMkernel also has vNICs for VMotion and IP storage network requirements. Each ESX host has its own virtual switches. On one side of the virtual switch are port groups that connect to virtual machines. On the other side are uplink connections to physical Ethernet adapters on the server where the virtual switch resides. Virtual machines, the service console, and VMkernel components connect to the outside world through the physical Ethernet adapters that are connected to the virtual switch uplinks. Virtuel Physique Cartes réseau physiques … Switchs physiques Hôte VMware ESXi 1 Hôte VMware ESX 2

36 Architecture Distributed Switch
… Groupes de ports distribués vMotion Machines virtuelles Console de service vCenter Server Distributed Switch (plan de contrôle) Console de service vSwitchs masqués (plan E/S) The new vNetwork components move network management to the datacenter level. This diagram shows the new networking architecture. First off we have distributed switches. These are managed entities configured inside vCenter. Distributed switches provide the same basic functions as standard vSwitches, but they exist across two or more clustered ESX or ESXi hosts. vCenter Server owns the configuration of distributed switches, and the configuration is consistent across all hosts. Like a VI3 standard vSwitch, a distributed switches connects to a physical network via one or more physical Ethernet adapters on the hosts included in the cluster. In this manner, physical NICs become clustered resources to use as required by the networked components. Each distributed switch includes distributed ports. A distributed port represents a port to which you can connect any networking entity, such as a virtual machine, the Service Console, and so on. vCenter Server stores the state of distributed ports in the vCenter database, so networking statistics and policies migrate with virtual machines when moved from host to host. This network VMotion feature is key to implementing state-dependent features such as inline IDS/IPS, firewalls, and third party virtual switches. Be careful not to confuse a distributed switch with a single switch spanning across several hosts. Two virtual machines on different hosts can communicate with each other only if both virtual machines have uplinks in the same broadcast domain. Consider a distributed switch as a template for the network configuration on each ESX or ESXi host. Virtuel Physique … Hôte VMware ESXi 1 Hôte VMware ESX 2

37 Enhanced vMotion Compatibility (EVC)
Disponibilité Sécurité Évolutivité Enhanced vMotion Compatibility (EVC) Fonctionnalités de base des processeurs CPUID K… CPUID CPUID CPUID X… X… X… VMotion is one example of an application service that helps deliver availability by reducing planned downtime that would otherwise be required for hardware maintenance and load balancing. Enhanced VMotion Compatibility (or EVC) is a new feature introduced in ESX 3.5 Update 2 and VirtualCenter 2.5 Update 2. EVC facilitates safe VMotion across a range of CPU generations. With EVC, it is possible to VMotion between CPUs which previously were considered incompatible. VMotion CPU compatibility relies on CPUIDs for system property information such as vendor name, CPU family and model, and supported features such as SSE3, SSSE3, and Nx/XD. EVC uses AMD-V Extended Migration and Intel® VT FlexMigration technologies to hide from the virtual machine CPUID feature bits which might otherwise cause VMotion incompatibilities. By hiding these incompatible features, it is possible to make newer CPUs compatible with older generation processors. EVC, however, does not hide CPU features like number of cores per CPU, cache size, or any other features that could potentially cause performance penalties. EVC works at the cluster level in the vCenter inventory using CPU baselines to configure all processors included in the EVC-enabled cluster. A baseline is a set of CPU features that is supported by every host in the cluster. When you configure EVC, you set all host processors in the cluster to present the features of a baseline processor. Once enabled for a cluster, hosts that are added to the cluster are automatically configured to the CPU baseline. Hosts that cannot be configured to the baseline are not permitted to join the cluster. Virtual machines in the cluster always see an identical CPU feature set, no matter which host they happen to run on. And since this process is automatic, EVC is very simple to use and requires no specialized knowledge about CPU features and masks. Cluster EVC EVC évite un échec des migrations effectuées avec vMotion en raison d’une incompatibilité des processeurs.

38 Storage vMotion dans vSphere 4
Disponibilité Sécurité Évolutivité Storage vMotion dans vSphere 4 Améliorations Possibilité de gérer via vSphere Client Prise en charge des protocoles NFS, Fibre Channel et iSCSI Plus besoin de disposer du double de la mémoire Possibilité de faire passer les VMDK du format standard au format fin Possibilité de faire migrer des RDM vers des RDM et des RDM vers des VMDK (sans passthrough) Utilisation des nouvelles fonctions de vSphere 4 pour accélérer la migration Restrictions Les machines virtuelles ne peuvent pas comporter de snapshots Les VM doivent être désactivées pour faire migrer simultanément l’hôte et la banque de données ESX introduced the concept of Storage VMotion so that you could create a VMFS 3 volume, and then migrate the virtual machines from a shared VMFS 2 volume to the new VMFS 3 volume without any downtime. Data transfer occurred only in the ESX host so there was no network connectivity issue. New updates to Storage VMotion were included in ESX 3.5. In this version virtual machines remain on the same host, but their disks can be moved to other datastores. The process requires no downtime, is transparent to guest operating systems and applications and has minimal impact on performance. Administration is done via the Remote Command Line Interface and APIs. vSphere 4 Storage VMotion includes even more enhancements. In addition to the Command Line Interface and APIs, you can use the vSphere Client to administer Storage VMotion. And, Storage VMotion will now work across NFS in addition to Fibre Channel and iSCSI. The last version of Storage VMotion required that the host have enough resources to support two instance of the virtual machine; however, this is no longer a requirements. Storage VMotion now provides the option to convert virtual disks from thick to thin formats. It also supports migrating RDMs to RDMs. And for virtual machines that have not been configured to use VMwareDirectPath I/O, you can use Storage VMotion to convert RDMs to VMDKs. Finally, Storage VMotion leverages features new to vSphere 4. For example, Storage VMotion uses fast suspend/resume and change block tracking. We’ll explain more about those features in just a minute. Storage VMotion in vSphere 4 does included a couple of limitations worth noting. First, this version does not support migrating virtual machine that have snapshots. And, you cannot migrate virtual machines to a different host and a different datastore simultaneously unless you power off the virtual machine.

39 VMware Fault Tolerance (FT)
Disponibilité Sécurité Évolutivité VMware Fault Tolerance (FT) Technologie vLockstep Technologie vLockstep Principale Secondaire Nouvelle principale Nouvelle secondaire For mission critical applications that can tolerate no downtime or data loss, vSphere 4 introduces VMware Fault Tolerance, or FT. When you enable FT on a virtual machine in an HA-enabled cluster, FT creates a duplicate, secondary, copy of the virtual machine on a different host. Then, Record/Replay technology records all executions on the primary virtual machine and replays them on the secondary instance. vLockstep technology ensures the two copies stay synchronized and allows the workload to run on two different ESX/ESXi hosts simultaneously. To the external world, the virtual machines appear as one virtual machine. That is, they have one IP address, one MAC address, and you need only manage the primary virtual machine. Heartbeats and replay information allow the virtual machines to communicate continuously to monitor the status of their complementary virtual machine. If a failure is detected, FT creates a new copy of the virtual machine on another host in the cluster. If the failed virtual machine is the primary, the secondary takes over and a new secondary is established. If the secondary fails, another secondary is created to replace the one that was lost. FT provides a higher level of business continuity than HA but requires more overhead and resources than HA. In the event of a failure, the secondary immediately comes on-line, and all or almost all information about the state of the virtual machine is preserved. Applications are already running, and data stored in memory do not need to be re-entered or reloaded. VMware HA, on the other hand, restarts virtual machines after a failure. Restarting the virtual machine requires the virtual machines to complete the process of rebooting, and there is a chance that information about the state of the virtual machine, such as applications or unsaved user-entered may be lost. Several typical situations can benefit from the use of VMware FT. For example: Applications that needs to be available at all times, especially those that have long-lasting client connections to maintain during hardware failure, can benefit from FT. And FT is useful in cases where high availability might be provided through Microsoft Cluster Service, but Microsoft Cluster Service is too complicated to configure and maintain. Or, you can use FT for custom applications that have no other way to configure clustering. VMware FT protège les machines virtuelles dans un cluster HA contre toute interruption de service et perte de données.

40 Activation de Fault Tolerance d’un simple clic
Disponibilité Sécurité Évolutivité Activation de Fault Tolerance d’un simple clic Machine virtuelle principale > Onglet Summary Une fois Fault Tolerance activé, l’onglet Status de la machine virtuelle principale affiche les informations de Fault Tolerance. To enable fault tolerance for a virtual machine, simply right click the virtual machine in the inventory and select Fault Tolerance > Turn On Fault Tolerance. vCenter Server creates the virtual machine with the same name as the primary virtual machines, but indicates that it is the copy by placing the word secondary in parentheses after the name. You use the same process from the primary virtual machine to turn the feature off. You cannot disable FT from the secondary virtual machine.

41 Disponibilité Sécurité Évolutivité VMware Data Recovery Solution VMware de sauvegarde/ restauration fondée sur des API de protection des données Sauvegarde et restauration sur disque sans agent Suppression des doublons et sauvegardes incrémentielles pour économiser l’espace disque VMware Data Recovery is a new backup and recovery product from VMware. It is managed via a vCenter Server plugin and uses the vStorage APIs for Data Protection. It is designed for small to medium size organizations who do not currently have a backup solution or who are looking for a backup solution that it optimized for virtualization. When you open Data Recovery in the vSphere Client for the first time, Data Recovery provides a simple interface to perform basic configuration, such as defining network parameters. After that, wizard interfaces allow you to quickly create, configure and schedule backup jobs. Data Recovery is an agentless, disk-based solution, allowing for faster restores over solutions that write to backup tape. You can restore individual files or entire images. Multiple restore points for each virtual machine are displayed to easily select a copy to restore from a specific point in time. Data Recovery utilizes built in data de-duplication technology to save significant disk space. De-duplication eliminates duplicate storage blocks as backup data is streamed to disk. Therefore, you can maintain multiple point-in-time copies of virtual machines using only a fraction of the storage. To efficiently utilize the backup window and available resources, the de-duplication operation occurs as the virtual machine backup is stored to disk

42 Système d’exploitation
Disponibilité Sécurité Évolutivité VMware VMsafe API assurant la protection des VM par l’inspection de composants virtuels, en relation avec l’hyperviseur Moteur de protection isolé des logiciels malveillants Couverture étendue du réseau, du stockage, de la mémoire et du processeur des machines virtuelles Application VMware VMSafe, announced earlier in 2008, is a set of APIs that enable protection of VMs by a protection engine : Works with the hypervisor to inspect a VM’s mem, cpu and storage from a higher privilege point Is isolated from the malware Covers all aspects of security – not limited to network or host. VMware VMSafe based products from our security partner ecosystem will work with VMware vSphere™ editions to provide higher levels of security than even physical systems MORE DETAIL Security solutions have an inherent problem. Protection engines are running in the same context as the malware they are protecting against and as a result, malware is able to subvert these engines by simply using the same hooks into the system as the protection engine. Worse, with Longhorn and Vista, Microsoft has enabled Patchguard, effectively eliminating the kernel hooks available to both the security solutions and the malware. While this helps, it doesn’t change the fact that malware and rootkits still exist and can run in those environments. The context that these security solutions need to protect against is also not limited to one set of interactions (e.g. attacks from the network and from spyware and from rootkits). Even those solutions that are in a safe context (outside the OS), they can’t see information from other contexts (e.g. network protection has no host visibility). Security API’s built into the hypervisor allow for 2 key advantages: Better Context – Provide protection from outside the OS, from a trusted context New Capabilities – now they can view all interactions and contexts Now, new security solutions can be developed and integrated within the VMware virtual infrastructure and we can protect the VM by inspection of virtual components (CPU, Memory, Network and Storage). Provides complete integration with VMotion, Storage VMotion, HA, etc. for any new security solution using the API’s. The end-result is an unprecedented level of security for VMs that’s better than the physical infrastructure. These API’s are already being made available to the security ISVs ecosystem. We utilize VC for role-based privileges to assign protection to any single VM and VMware certifies the solutions developed by our partners to ensure the security VM is created by a real security ISV and not a malicious hacker. Some potential use cases: An AV virtual appliance that intercepts all storage IO and is able to scan files as they are read/written from disk. This can be done without loading an AV agent on each machine. Inline Network Security for each ESX host. Now you can ensure that ALL network IO traffic is inspected by an inline appliance, regardless of your virtual networking setup. This includes even inter-VM traffic and allows state to be transferred from host to host during VMotion so that the security protection is never lost. Système d’exploitation Moteur de protection VMware vSphere™ 42

43 vShield Zones Fonctionnalités Avantages
Disponibilité Sécurité Évolutivité vShield Zones Fonctionnalités Isolement, liaison par passerelle ou protection par pare-feu des zones de VM en fonction de conteneurs VI familiers Surveillance des activités autorisées ou refusées à l’aide de protocoles basés sur des applications Blocage en un seul clic d’un trafic réseau précis au niveau du flux vers le pare-feu Avantages Stratégie de sécurité bien définie au sein de l’environnement virtuel Surveillance et règles sécurisées, même via vMotion et les événements du cycle de vie des VM Règles simples basées sur des zones réduisant les erreurs de procédure vShield Zones is a new Application Service providing fundamental and critical network security for vSphere deployments Expanding virtualization deployments in the datacenter are encompassing multiple areas of trust such as DMZ (demilitarized zone) buffers to the Internet and sensitive data such as credit card information subject to Payment Card Industry (PCI) compliance or corporate financial data covered by Sarbanes-Oxley. These varying trust zones must be segmented with firewalls and other network security. Existing physical appliances require diverting traffic to external chokepoints, splintering ESX resource pools into small fragments and disrupting the seamless vision of an internal computing cloud. vShield Zones is a virtual appliance that allows you to monitor and restrict inter-VM traffic within and between ESX hosts to provide security and compliance within shared resource pools. vCenter integration lets you create network zones based on familiar VI containers such as clusters and VLANs vShield Zones scans VM’s for known applications to present network flows and security policies by application protocol rather than as raw network flows. Virtualization awareness and application awareness increases accuracy and reduces risk of misconfiguration and noncompliance. Consistent security policies can be assured throughout a VM lifecycle, from initial provisioning to VMotion across various hardware to final decommissioning. Complete view of virtual machines, networks and security policies allows you to audit security posture fully within the virtual environment to meet defined security SLA’s, irrespective of changes to your external physical network and perimeter. 43 43

44 Disponibilité Sécurité Évolutivité Évolutivité de l’hôte Optimisation des performances et taux de consolidation accrus VMKernel 64 bits Mémoire hôte de 512 Go 64 processeurs logiques 256 machines virtuelles par hôte Appl. OS 32 cœurs 256 Go 192 MV 512 Go 64 cœurs 256 MV The ESX/ESXi hypervisor continues to lead the industry with highly scalable support for large servers with high core counts and memory configurations. The VMkernel, a core component of the ESX/ESXi 4.0 hypervisor, is now 64-bit. This provides greater host physical memory capacity, enhanced performance and more seamless hardware support than earlier releases. ESX/ESXi 4.0 supports systems with up to 512GB of RAM. And, ESX/ESXi 4.0 provides headroom for more virtual machines per host and the ability to achieve even higher consolidation ratios on larger machines. 44 44

45 Évolutivité de la machine virtuelle
Disponibilité Sécurité Évolutivité Évolutivité de la machine virtuelle L’extension de la capacité permet de gérer des charges de travail bien plus importantes Virtual SMP octodirectionnel 256 Go de mémoire RAM Version 7 du matériel de la machine virtuelle Nouveaux périphériques virtuels E/S VMDirectPath Prise en charge de l'installation à chaud 256 Go 8 processeurs Appl. OS Virtual machines themselves can now scale to accommodate even the largest workloads. And, you can scale up without powering down the virtual machine. ESX/ESXi 4.0 provides support for virtual machines with up to 8 virtual CPUs, allowing larger CPU-intensive workloads to be run on the VMware ESX platform. It is also possible to assign any integer number of virtual CPUs between 1 and 8 to a virtual machine. Up to 256GB of RAM can be assigned to ESX/ESXi 4.0 virtual machines. ESX/ESXi 4.0 introduces Hardware version 7, which adds significant new features including new storage and networking virtual devices. We’ll talk a little more about those in just a minute. Hardware version 7 also includes support for VMDirectPath I/O device access. VMDirectPath I/O enhances CPU efficiency in handling workloads that require constant and frequent access to i/o devices by allowing virtual machines to directly access the underlying hardware devices. Hardware version 7 also provides support for adding and removing virtual devices, adding virtual CPUs, and adding memory to a virtual machine without having to power off the virtual machine. Hardware version 7 is the default for new ESX/ESXi 4.0 virtual machines. Virtual machines that use hardware version 7 features are not compatible with ESX/ESXi releases prior to version 4.0. However, ESX/ESXi 4.0 will continue to run virtual machines created on hosts running ESX Server versions 2.x and 3.x. 45 45

46 Principales fonctionnalités de vCenter Server 4
Évolutivité accrue vCenter Server Linked Mode vCenter Orchestrator Rationalisation de la gestion Host Profiles vApps Centralisation de la gestion des licences Mises à jour du plug-in de vCenter Server Gestion des ressources Améliorations des tableaux des performances Optimisation de la détection du stockage vCenter Server 4 improves scalability, streamlines many management processes, and adds new features for better resource management. performance management, reduces storage management costs, and reduces the complexity involved with setup and ongoing management of virtual environments. This table shows some of the many new features and enhancements.

47 Présentation de vCenter Server Linked Mode
Le client vSphere standard a accès aux données d’inventaire sur plusieurs serveurs vCenter Server Consultation et recherche dans les données d’inventaire d’un groupe de serveurs vCenter Server Rôles et configurations de licence partagés vCenter Server 4 introduces the ability to join multiple vCenter Servers into a linked‐mode group. Then you can use the vSphere Client to log on to any single instance of vCenter Server and view and manage the inventories of all the vCenter Servers in the group. Each user sees only the vCenter Server instances for which they have valid permissions. There are several reasons why you may want to link vCenter Servers. For example, you may want to simplify management of inventories associated with remote offices or multiple datacenters. Likewise, you could use Linked Mode to configure a recovery site for disaster recovery purposes. vCenter Server Linked Mode allows for: Global role definitions Searches for inventory items across multiple vCenter Server instances And a license model across multiple vCenter Servers

48 Bibliothèque de workflows
vCenter Orchestrator Utilisez Orchestrator pour créer et exécuter des workflows qui automatisent les processus de gestion de l’infrastructure virtuelle Moteur de workflow vCenter Server XML SSH … Plug-in tiers Client Configuration Bibliothèque de workflows Service Web vCenter Server 4 includes a new orchestration platform and development components that installs silently when you install vCenter Server 4. vCenter Orchestrator provides a library of extensible workflows to create and execute automated, configurable processes to manage the vSphere datacenter infrastructure. To understand how Orchestrator works, it’s important to understand the difference between automation and orchestration. Automation provides a way to perform a frequently repeated process without manual intervention. Using a Perl or a PowerShell script to add several ESX hosts to the vCenter Server inventory is an example of automation. Orchestration, on the other hand, provides a way to manage multiple automated processes across heterogeneous systems. An example of orchestration is to automate the entire process of adding several ESX hosts to vCenter Server, updating the CMDB, and sending an notification. vCenter Orchestrator relies on workflows to create and execute automated processes. Workflows are reusable building blocks that combine actions, decisions, and results that, when performed in a particular order, complete a specific task or process in a virtual environment. Workflows can call upon other workflows, so for example, you can reuse a workflow that starts a virtual machine in several different workflows. Orchestrator provides a library of more than 400 workflows that encapsulate best practices for common virtual environment management tasks such as provisioning virtual machines, backing up, and performing regular maintenance. Orchestrator also provides libraries of the individual actions that the workflows execute. Orchestrator includes several components to create and execute workflows. The Orchestrator Workflow Engine assembles workflows from the building blocks provided in the Orchestrator's libraries of pre-defined objects and actions. One such library exposes every function of the vCenter Server API, allowing you to integrate all the functionality provided by vCenter Server into your workflows. Another Orchestrator library provides Java database connectivity functions that allow you to automate processes related to database administration in your workflows. A third library provides XML processing operations, and so on. The workflow engine can also take objects from external libraries that you plug into Orchestrator, allowing you to create your own tailor-made processes or implement functions provided by third-party applications. The Orchestrator Web Service starts workflows and manages their execution via a network or the Web. Orchestrator includes two user interfaces accessed from the Start menu of the vCenter Server: Use the Orchestrator Configuration interface to configure the components that are related to the workflow engine, such as network, database, LDAP, server certificate, and so on. Use the Orchestrator Client to access the workflow engine to create workflows. You cannot open the Client until Orchestrator has been configured properly. To learn about configuring and using Orchestrator, see the vCenter Orchestrator Administrator’s Guide. To learn about develop applications using Orchestrator, see the vCenter Orchestrator Developer's Guide.

49 Workflow de base pour mettre en œuvre Host Profiles
Profil d’hôte Réservation de mémoire Stockage Réseau Date et heure Pare-feu Sécurité Services Utilisateurs et groupes d’utilisateurs 2 4 3 The basic workflow to implement host profiles is: One: Set up and configure a host to use as the reference host. Two: Use the Create Profile wizard to create a profile from the reference host configuration. Then, optionally, you can edit the profile to further customize the policies within the profile. We’ll talk more about editing policies in just a minute. Three: Attach the host profile to other hosts or clusters of hosts. Four: Check to ensure that the hosts to which the host profile is attached are in compliance with the profile. And Five: Apply the profile to the hosts that are not in compliance. 5 Cluster 1 Hôte de référence

50 Utilisation de Host Profiles
Après avoir créé le profil, associez-le à des hôtes/clusters afin de pouvoir vérifier leur conformité et appliquez-le aux hôtes non conformes. After configuring a host profile configuration, you can use the Attach Host/Cluster command to associate a cluster or individual hosts with the profile. Then, after the profile is associated with hosts, you can use the Check Compliance Now link to ensure that the associated hosts remain in compliance with the profile. If the check discovers a non-compliant host, those policies configured differently than the reference host profile show in the Compliance Failures section. To bring a non-compliant host back into compliance, place the host in maintenance mode and click Apply Profile.

51 Couche de virtualisation distribuée
Présentation de vApp Les vApps sont des services d’applications n-tier que vous pouvez gérer comme un seul élément d’inventaire. Permet une gestion en une seule étape Supprime les installations et les configurations complexes Serveur d’appl. VM vApp Descripteur OVF Base de données Pool de ressources vApps extend the capabilities of virtual appliances to encapsulate a multi-tier application running on multiple virtual machines. vApps encapsulate not only virtual machines but also their interdependencies and resource allocations allowing for single-step power operations, cloning, deployment, and monitoring of the entire service. vSphere includes end-to-end vApp support including creating, running, and updating vApps as well as importing and exporting them in compliance with Open Virtualization Format 1.0 standard. The OVF file format allows for exchange of virtual appliances across products and platforms. The OVF format offers several advantages: OVF files are compressed, allowing for faster downloads. vCenter validates an OVF file before importing it, and ensures that it is compatible with the intended destination server. And OVF files provides for rich metadata, so you can describe important characteristics such as the vApp anatomy, it’s relationship to other virtual machines, and resource and availability requirements. Couche de virtualisation distribuée …

52 Gestion simplifiée des licences avec vSphere 4
Simples clés de licence au lieu de licences Flex 1 licence par édition 1 clé pour de nombreux hôtes Nouvelle administration centralisée des clés de licence dans vCenter Aucun serveur de licences distinct à gérer ou à surveiller Surveillance centralisée des hôtes et des licences via vCenter, ce qui simplifie la conformité Le nouveau portail des licences offre une vue plus précise des droits vSphere 4 introduces centralized license reporting and management. Key theme: simplification! Better match between how licenses are sold and how they are used. The key points about the new licensing: Flex licensing is replaced by simple license keys New centralized license key administration in vCenter New license portal provides more accurate view of entitlement

53 Améliorations du plug-in de vCenter Server
Moins de surcharge et meilleure évolutivité Plug-in modulaire Analyse jusqu’à 500 machines physiques à la fois Davantage de plates- formes prises en charge Possibilité de conversion vers de nouvelles plates-formes prises en charge par VMware ESX/ESXi 4.0 Prise en charge de Windows Server comme source et  plate-forme Convertit les VM Microsoft Hyper-V en VM VMware Gestion et administration améliorées Mises à jour d’hôtes VMware ESX/ESXi et d’appliances virtuelles Groupes de base Tableau de bord de conformité Transfert de correctifs The Guided Consolidation service is now a vCenter Server modular plugin and can be installed on a different system than the vCenter Server. This change allows vCenter Server to perform optimally with lower overheads around consolidation operations. In addition, the Guided Consolidation service provides better scalability by concurrently analyzing and making consolidation recommendations for up to 500 physical machines at a given time. Guided Consolidation service by virtue of being internationalized is also able to discover and analyze systems running non-English versions of Windows. This release of Converter includes three main enhancments: Converter can now import physical, virtual, and third party sources to all of the newly supported platforms on ESX/ESXi 4 hosts. Converter support sWindows Server 2008, both as a conversion source and as an installable platform. And, Converter can convert Microsoft Hyper-V virtual machines to VMware virtual machines by treating Hyper-V machines as physical source machines. There are several updates to Upgrade Manager for vSphere 4: Introduces two significant enhancements to baselines: you can now use Update Manager to upgrade ESX/ESXi hosts, virtual machine hardware, VMware Tools, and virtual appliances; and baseline groups allow you to specify an upgrade baseline and a set of patches in one group Update Manager also includes a new dashboard to review how machines comply with baselines and baseline groups. Update Manager includes a Stage wizard so that you can download patches from a remote server to a local server without applying the patches immediately. Staging patches speeds up the remediation process, because when the staged patches and upgrades are applied to a set of hosts the files are available locally.

54 Le nouvel onglet des vues de stockage donne un meilleur aperçu de l'infrastructure de stockage
The vSphere Client now includes a Storage Views tab for all managed entities in the vSphere inventory (except networks). This tab is powered by a new Web service within the vCenter Management Web services called the Storage Management Service. The Storage Management Service is designed to provide greater insight into the storage infrastructure, particularly in the areas of storage connectivity and capacity utilization. That means you can now quickly view information to answer questions such as: How much space on a datastore is used for snapshots? or Are there redundant paths to a virtual machine’s storage? All data used to compute information shown on the tab come from the vCenter Server database. The Storage Management Service makes direct database calls periodically, computes the information, and stores it in an in-memory cache. A display in the top, right corner shows the last time the report was updated and allows you to manually update as required. Le nouvel onglet des vues de stockage donne un meilleur aperçu de l’utilisation de la capacité et de la connectivité du stockage.

55 Prise en charge du système d’exploitation client
Prise en charge de plus de 45 systèmes d’exploitation clients Nouveautés de vSphere 4 Asianux 3.0 CentOS 4 Debian 4 FreeBSD 6 FreeBSD 7 OS/2 MS-DOS 6.22 Windows 3.1 Windows 95 Windows 98 OpenServer 5 Unixware 7 Solaris 8 (expérimental) Solaris 9 (expérimental) Solaris 10 ESX/ESXi 4.0 adds support for 13 new guest operating systems and experimental support for two more.

56 VMware vSphere™ s'intègre aux solutions des principaux partenaires
Services d’applications VMware vSphere™ s'intègre aux solutions des principaux partenaires Services d’infrastructure Clustering Protection des données Pare-feu Antivirus Prévention des intrusions Détection d’intrusion Dimensionnement dynamique des ressources Disponibilité Sécurité Évolutivité vSphere 4.0 vCompute vStorage vNetwork We’ve talked a lot about new features in vSphere 4, but we also wanted to emphasize that vSphere 4 is a platform designed to integrate with the capabilties provided by a broad array of VMware partners, giving customers access to a rich array of functionality that can be leveraged across their physical and virtual environment. Here are just a few examples of ways in which VMware partners are integrating with vSphere to deliver value-added functionality on top of the VMware platform. Assistance au niveau matériel Compatibilité optimisée avec la migration à chaud Gestion du stockage et réplication Appliances de stockage virtuelles Gestion de réseau

57 Merci

58 Licences et supports Vmware
Licences Vmware vSphere 4 Licences Vcenter 4 Les packages Les licences View Les différentes couvertures de support Vmware

59 VMware : vSphere les plateforme de base
VMware : vSphere les plateforme de base Nouveau Gestion à grande échelle des applications de production stratégiques Host Profiles Distributed Switch DRS/DPM DRS/DPM Storage vMotion Storage vMotion Produits haute disponibilité pour la protection des applications de production stratégiques vShield Zones vShield Zones vShield Zones Data Recovery Data Recovery Data Recovery Fault Tolerance Fault Tolerance Fault Tolerance Ajout à chaud Ajout à chaud Ajout à chaud vMotion™ vMotion™ vMotion™ Thin Provisioning Thin Provisioning Thin Provisioning Thin Provisioning High Availability High Availability High Availability High Availability Update Manager Update Manager Update Manager Update Manager Consolidation de base d’un environnement de tests/développement, ou de taille réduite API vStorage/VCB API vStorage/VCB API vStorage/VCB API vStorage/VCB VC Agent VC Agent VC Agent VC Agent vSMP quadridirectionnel vSMP quadridirectionnel vSMP quadridirectionnel vSMP octodirectionnel VMware ESXi OU VMware ESX VMware ESXi OU VMware ESX VMware ESXi OU VMware ESX VMware ESXi OU VMware ESX 6 cœurs physiques/ CPU 256 Go mémoire physique 12 cœurs physiques/ CPU 256 Go mémoire physique 6 cœurs physiques/ CPU 256 Go mémoire physique 12 cœurs physiques/CPU STANDARD ADVANCED ENTERPRISE ENTERPRISE PLUS

60 vCenter Server 4 vCenter Server est requis pour la plupart des fonctionnalités vSphere Gestion VI Licence SnS (Gold/Plat.) vCenter Server Standard et vCenter Server Foundation sont des serveurs de gestion vCenter Server Foundation est limité à 3 nœuds de toute taille par suite Une instance est requise pour la plupart des fonctionnalités vSphere Standard, Advanced ou Enterprise Plus vCenter Server Standard 4 588 € 964/1 147 € Pas de limite en nombre d’hôtes Inclut Linked Mode Inclut Orchestrator vCenter Server Foundation 1 373 € 501/593 € Limité à 3 hôtes ESX vCenter Heartbeat 9 181 € 1 928/2 296 € Par instance (Euro €)

61 VMware : Nouvelles éditions de vSphere 4 : présentation
VMware : Nouvelles éditions de vSphere 4 : présentation VMware vSphere STANDARD (730 €/ processeur) Consolidation simple ADVANCED (2 062 €/ processeur) Disponibilité ENTERPRISE (2 641 €/ processeur) Gestion automatisée des ressources ENTERPRISE PLUS (3 211 €/ processeur) Opérations simplifiées ESSENTIALS PLUS Solution de disponibilité intégrée pour les petites entreprises (2 751€ tout-en-un pour 3 serveurs) Gestion de base pour : Consolidation simple Sites distants Environnements de tests Haute disponibilité pour : Infrastructure de production Applications stratégiques Gestion automatisée des ressources pour : Infrastructure de production Applications stratégiques Gestion et intégration à grande échelle pour : Cloud interne Applications Tier 1 ESSENTIALS Gestion de base d’ESXi (gratuit) (914 € tout-en-un pour 3 serveurs) Évolutivité limitée, faible prix initial, fonctionnalités ciblées pour petits sites Évolutivité illimitée, prix avantageux, faible TCO, fonctionnalités complètes

62 VMware : Les offres Essentials
VMware : Les offres Essentials Offres tout inclus : Licences pour 3 serveurs physiques (jusqu’à 2 processeurs chacun) Licence pour serveur de gestion centralisée Les offres ne peuvent pas être dissociées ni combinées ; les composants ne peuvent pas être utilisés avec d’autres éditions de vSphere Data Recovery x 6 processeurs High Availability x 6 processeurs 6 processeurs x Update Manager Update Manager x 6 processeurs 6 processeurs x VC Agent VC Agent x 6 processeurs 6 processeurs x vSMP octodirectionnel vSMP octodirectionnel x 6 processeurs 6 processeurs x VMware ESXi OU VMware ESX VMware ESXi OU VMware ESX x 6 processeurs vCenter Server pour Essentials (jusqu’à 3 srvs) vCenter Server pour Essentials (jusqu’à 3 srvs) x 1 1 x vCenter Server pour Essentials ESSENTIALS ESSENTIALS PLUS

63 Les offres de support VMware
PLATINUM GOLD SILVER Temps de réponse Accès Horaires Nombre d’appels Produits Maintenance logicielle Contacts 30 min-12 heures (en fonction de la sévérité) Web et Téléphone 7 x 24 x 365 Illimités Tous sauf Fusion et Player Mises à jour mineures et majeures Six 4-24 heures (en fonction de la sévérité) Web et Téléphone Lun-Ven 6h-18h Illimités Tous sauf Fusion et Player Mises à jour mineures et majeures Quatre 8-24 heures (en fonction de la sévérité) Web seulement Lun-Ven 6h-18h Illimités VMware Workstation (uniquement) Mises à jour mineures et majeures Deux

64 Questions / Réponses