Microsoft SCVMM and HyperV virtualization functions are now available through Tivoli Provisioning Manager's(220.127.116.11) Image library features. Image library maps image repositories from across virtualization technologies and provides the capability to capture , manage and deploy images of virtual machines.
TPM controls the Hyper-V host platform servers and virtual machines through Powershell APIs exposed by Microsoft System Center Virtual Machine Manager (SCVMM).
Image library terminology
Image Repository – Can be master-enabled (supports master images) , saved-enabled (supports saved/cloned images) , instance-enabled(instance VMs can be deployed on them). (In case of Vmware , the single entity “datastore” represents all of them)
Master images – In case of Vmware and HyperV , native Vmware/SCVMM templates are discovered as master images that can be deployed to create new instances.
Saved/Cloned images – A complete backup image taken of a VM that can be used to restore and replace (if existing) the VM. In case of Vmware , it is created by cloning and creating backup on the host (just like cloning any other VM)
Instance images – Instance VMs lying on the host with a reference to their source master/saved images (if any)
SCVMM - System Center Virtual Machine Manager
HyperV library server - The Virtual Machine Manager (VMM) library is a catalog of resources you can use to create and configure virtual machines in VMM. The library contains files stored on library shares, and it contains operating system, hardware, and template configurations stored in the VMM database. Virtual machines that are not in use can be stored in the library.
HyperV hosts , host groups , clusters
SCVMM templates (just like Vmware templates – hardware and software templates)
Integration services (just like Vmware tools)
Checkpoints (just like Vmware snapshots)
Host disks (No concept of separate entities like datastores , physical disks/SAN mounted as Windows drives
Discovery of two kinds of image repositories and their mapping with HyperV:
with a SCVMM will be discovered as image repositories during SCVMM
discovery.These repositories will be master-enabled
(since SCVMM templates lie on library servers itself) and will also
(saved images feature is designed to create the images by cloning on
the library server in a “stored” state , instead of occupying
HyperV expects you to pass the complete Virtual Machine placement location during creation. This location represents where the vhd and other config files lie. Each host has a configurable list of “placement locations” that a user could choose from. Every VM placement location for a particular host would be represented as a unique “instance-enabled repository” with a mount point value as the location.This would result in “n” number of instance repositories to choose from during deployment (for a particular host) , where “n” is the number of VM placement locations configured for that host.A user can also create his own custom instance repository with a mount point value of his choice of VM location.
Master images (SCVMM templates) and instance images (Virtual machines)
Template discovery will create/reconcile master images alongiwth hardware configuration parameters (based on uniqueness).Master images will lie on an image repository (based on the library server it lies on) .Master images can be deployed on any instance repository , which will trigger SCVMM template deployment workflow and create an instance image on success. Master images can be deleted resulting in deletion of SCVMM template
Save and Restore images
Save Image operation allows you to clone a source VM on a host to a library server (saved-enabled image repository).The VM in the library server lies in “stored” state and does not take up host resources.
Restore operation clones a VM from the library server to a host .A saved image can be restored on to any host platform either by replacing the existing VM (if the source VM DCM association exists) or by creating a new VM. If restore takes place by replacement , the new VM is mapped to the same DCM object id of the old VM.Restored image is powered on we wait for integration services to startup (to discover IP and networking info).Restore operation requires you to select a instance repository for the chosen host.
Synchronize image repositories
“Template only” discovery is an important requirement and is very less time consuming. A master-enabled repository (library server) can now be synchronized which reconciles all the SCVMM templates existing in that library server with master images.
Instance images are linked to the source master/saved image. When an instance-enabled repository is synchronized , all Vms lying on that particular instance repository mount point are reconciled (with or without a source image).If a corresponding server object does not exist , a new DCM entry is created and a VM only discovery is run for that VM.
These image library functions can also be harnessed by Tivoli Service Automation Manager to support various use-cases for the cloud.