Deploying Virtual Machines Overview

Deploying Virtual Machines

• Virtual Machines are the foundation of virtual infrastructure
• Deploying VMs effectively involves understanding different types of virtual hardware
• Skills required include:
  • Creating, cloning, and managing VMs and templates
  • Modifying VMs
  • Updating templates

Creating Virtual Machines

• Provisioning can be done in several ways:
  • Using the New Virtual Machine wizard
  • Deploying VMs from existing clones or templates
  • Deploying VMs from OVF templates

Virtual Machine Hardware Deep Dive

• Deployment method depends on factors such as infrastructure size, type, and goals
• The New Virtual Machine wizard is used for single VM creation if no existing VM meets requirements
• A single VM can be created, have an OS installed, and be used as a template for cloning VMs
• VMs, virtual appliances, and vApps stored in OVF format can be deployed
• A virtual appliance is a VM that typically has an OS and other software preinstalled
• OVF templates can be deployed from local file systems, removable media, shared network drives, and URLs
• VMware Host Client can be used to create a VM using OVF files

Modifying Virtual Machines

• VMware Tools are important for guest OS integration and optimal performance
• VMware Tools must sometimes be reinstalled after a VM is modified

Creating Templates and Cloning VMs

• Cloning a VM creates an exact copy of the original
• Cloning is an alternative to deploying a VM from a template
• The source VM can be powered on or off
• Cloning can be done via the vSphere Client

Introduction to Content Libraries

• Content libraries are used to store and manage OVF templates, ISO images, and other file types
• Libraries allow for centralized storage and sharing of content, making virtual infrastructure more efficient
• Content libraries can be used to create a central repository for templates, images, and files
• Content libraries can be published and subscribed to by other libraries

Subscribing to Content Libraries

• Content libraries can be published, allowing other libraries to subscribe to and download content
• The content library keeps content up to date by periodically synchronizing with the publisher
• Content can be stored in one of three types of libraries:
  • Local (controlled by the administrator)
  • Published (local library available for subscription)
  • Subscribed (a library that synchronizes with a published library)

Managing Templates in a Content Library

• Content libraries are stored in a vSphere datastore
• Sharing and consistency are major benefits of content libraries
• Administrators can perform the following functions using content libraries:
  • Store and share content (templates, ISO images, scripts)
  • Perform distributed file management
  • Synchronize content libraries across sites and vCenter instances
  • Mount ISO files directly from a content library
  • Maintain versions of VM templates

Content Library Types

• Administrators can change content in local or published libraries
• Users cannot change content in subscribed libraries
• Subscribed libraries cannot be published
• Local libraries are the simplest form
• A local library is created on a single vCenter instance and can be published
• A published library can be accessed by other vCenter instances
• A subscribed library synchronizes with a published library
• A subscribed library can contain copies of published library files or only metadata
• Published libraries can be on the same or different vCenter instances
• Content can only be added to local or published libraries

Publishing a Content Library

• A local library can be enabled for publishing
• Password protection can be added to published libraries
• A subscription URL allows subscribed libraries to access the published library
• When new VM templates are added to the published library, they must be published for the subscribed library to receive them
• vSphere uses linked clone technology to clone a VM template on checkout
• The original VM template remains available in the content library for deployment
• The changes made to the cloned VM are merged with the VM template and the clone is destroyed to update the template

Checking In the VM to the Template

• After changes are made to a VM, it is checked in to the template
• The Check In notes box is required
• The checked out VM can be discarded to avoid creating new versions of the template
• The checked out VM can be discarded to prevent other users from using a faulty version
• The Check In process merges changes into the master template and updates the template

Deploying VMs with the New Virtual Machine Wizard

• The New Virtual Machine wizard in the vSphere Client allows you to create VMs.
• Selecting a creation type is the first step.
• VMware Tools installation instructions for specific guest operating systems are available at [link].

Deploying OVF Templates

• Deploy any VM or virtual appliance stored in OVF format (preconfigured VMs).
• Virtual appliances are usually designed for a single purpose and are available on the VMware Marketplace.
• May require modifications to VM configuration (e.g., adding a network adapter or a virtual disk).
• VM changes can be made while the VM is powered off, while some hardware changes can be made while the VM is powered on.

Hot-Pluggable Devices

• Add resources to a running VM using the hot plug option.
• Examples of hot-pluggable devices include USB controllers, Ethernet adapters, and hard disk devices.
• Supported guest operating systems can also add CPU and memory while VM is powered on.
• Adding or removing devices from a physical server requires physical interaction. Using VMs allows adding resources dynamically without disrupting service.
• Shutting down a VM is required to remove hardware; reconfiguration can be done without entering the data center.
• Requirements for CPU and Memory Hot Plug features: VMware Tools installation, VM using Hardware version 11 or later, guest OS supporting hot-plug, and activation of the hot-plug features in VM settings.

Dynamically Increasing Virtual Disk Size

• Increase the size of a virtual disk belonging to a powered-on VM without snapshots attached.
• May require system tools to make the new space usable.
• Converting a VM to a template allows updating the template with new patches or software without creating a new template.

Deploying VMs from a Template

• Deploy a VM by providing information like VM name, inventory location, host, datastore, and guest operating system customization data.
• Cloning a powered-on VM does not quicence services and applications during the cloning process.
• Deploying from a template provides the same base image for all VMs, while cloning from a running VM may not create identical VMs due to activity happening within the VM.
• Templates use disk space; plan your disk space requirements.
• Deploying from a template is faster than cloning, especially when deploying many VMs at a time.

Guest Operating System Customization

• Customize aspects of the guest operating system when deploying from a template or cloning a VM.
• Customizable details include computer name, network settings, license settings, time zone, administrator or root password, and Windows Security Identifier.
• Customization helps prevent conflicts caused by identical settings in newly deployed VMs and their source.
• Without customization, VMs retain the host name, IP address, etc., from the source VM or template.

About Customization Specifications

• Create a customization specification to prepare the guest operating system.
• Specifications are stored in the vCenter database.
• Support is available for Windows and Linux guests.
• Manage customization specifications through Policies and Profiles in the main menu.

Customizing the Guest Operating System

• Use customization specifications to prepare the guest operating system when cloning a VM or deploying from a template.

Content Libraries

• Content libraries store and share content like templates, ISO images, scripts, and other file types.
• Centralized storage for content is achieved through published content libraries.
• Content libraries can be subscribed to and downloaded, ensuring the latest versions are available.
• Content libraries are stored on vSphere datastores.

Benefits of Content Libraries

• Storage efficiency and consistency are key reasons to install and use content libraries.
• Content libraries allow distributed file management, content synchronization across sites and vCenter instances, direct ISO mounting, and version maintenance of VM templates.
• Centralized content for a main vCenter instance helps manage and distribute original copies of OVF templates, ISO images, scripts, and other file types.
• Published content libraries allow other libraries to subscribe and download exact copies, updating when content changes.
• Rollback to previous versions of VM templates is possible.

Content Library Types

• Local: Controlled by the administrator.
• Published: Local library available for subscription.
• Subscribed: Synchronizes with a published library.
• Administrators can change content in local or published libraries. Users cannot change content in subscribed libraries, and subscribed libraries cannot be published.
• Local libraries are the simplest form.

This quiz covers the fundamentals of deploying virtual machines, focusing on different types of virtual hardware and effective provisioning methods. You'll explore skills necessary for creating, cloning, and managing VMs, as well as understanding deployment methods and configurations. Test your knowledge in the area of virtual infrastructure.