Download "user manual"

򐂰 Virtual machine management
VMM objects: Virtual CPU, Vendor Display Name, System UUID, Disk undoable behavior
13.3 Some scenarios that make use of the VMM enhancements
There are two different ways to make use of the VMM enhancements:
򐂰 The first way is the manual way to use the IBM Director console user interface to run
commands interactively.
򐂰 Another way is the automatic way to use the server function of IBM Director. For instance
to build actions and expanding actions could be launched through a scheduler with many
variations on constrains and define thresholds to trigger events that launches actions and
so forth.
Another goal is to show that there is no boundary between a real server and a virtual server.
The current version of VMM 1.0 has some limitations that do not allow a direct manipulation
on some VMware VirtualCenter or Microsoft Virtual Server objects such as creating a new
virtual machine. If you plan to use those functions you have to use the native management
interface from the vendors to deal with it.
13.3.1 Topology of the physical and logical servers
To better understand the scenarios and their context, we introduce the different physical and
logical servers and the terminology that we use in that context (the environment described
here is the same as shown in figure Figure 13-1 on page 310). This topology is as follows:
򐂰 VEWIN22 is the physical VMware VirtualCenter Server that gets all the management
capabilities in its domain.
Within VMware VirtualCenter you have two organizational objects: Farm Groups and
Farms. The only purpose for Farm Groups objects is to group Farms to logical units. There
is no equivalent mapping for Farm Groups through VMM into IBM Director.
򐂰 VE Farm is a logical organizational object that maps the VMware VirtualCenter object
Farm onto IBM Director.
The management capabilities for farm objects are in VMware VirtualCenter and all the
modifications have to take place into the VMware VirtualCenter.
򐂰 MSNESX1 is the physical VMware ESX Server that is member of the farm VE Farm on the
VMware VirtualCenter management domain VEWIN22. On this server two virtual
machines are installed.
򐂰 The virtual machines (logical hardware platform) VM 1 and VM 2 on the VMware ESX
Server MSNESX1 are, from an IBM Director standpoint ,a logical platform and have
therefore the IBM Director label (in the Groups column of IBM Director is a group named
Logical Platforms, open this group and you get in the Group Contents column all the
virtual machines displayed that are known by the IBM Director (see Figure 13-2 on
page 314).
Chapter 13. How to optimize an xSeries IT environment using IBM Director and Virtual Machine Manager
313