The Orchestrator provisioning manager provides the ability to manage the life cycle of virtual machines, as shown in the following figure.
Figure 9-1 VM Lifecycle Management
For more information about managing virtual machines, see the Novell ZENworks Orchestrator 1.2 Virtual Machine Management Guide.
While Orchestrator enables you you manage many aspects of your virtual environment, as a developer, you can create custom jobs that do the following tasks:
Discover resources that can be used as VM hosts.
Provision, migrate, and move VMs: Virtual machine images can be moved from one physical machine to another.
Check in VMs that have the proper versions and system configurations.
Provide checkpoints, restoration, and resynchronization of VMs: Snapshots of the virtual machine imge can be taken and used to restore the environment if needed.
Retire, delete, and destroy VMs: Jobs can decommission and retire deployed images.
Monitor VM operations: Jobs can start, shut down, suspend and restart VMs.
Manage on, off, suspend, and restart operations.
VM provisioning adapters run just like regular jobs on the Orchestrator. The system can detect a local store on each VM host and if a local disk might contain VM images. The provisioner puts in a request for a VM host. However, before a VM is brought to life, the system pre-reserves that VM for exclusive use.
That reservation prevents a VM from being stolen by any other job that’s waiting for a resource that might match this particular VM. The constraints specified to find a suitable host evaluates machine architectures, CPA, bit width, available virtual memory, or other administrator configured constraints, such as the number of virtual machine slots.
This process provides heterogeneous virtual machine management using the following virtual machine adapters:
There are two types of VMs:
A VM instance is a VM that is “state-full.” This means there can only ever be one VM that can be provisioned, moved around the infrastructure, and then shut down, yet maintains its state.
A VM template represents an image that can be clonable. After it is finished its services, it is shut down and destroyed.
It can be thought of as a “golden master.” The number of times a golden master or template can be provisioned or cloned is controlled though constraints that you specify when you create a provisioning job.