Resource mapping

This section provides information on mapping between virtual and physical resources when provisioning virtual machines.

When you instantiate a new virtual machine to run the App Connect HVE, you first must select a size for the virtual machine. As referenced in Requirements, the supported sizes are:

The preceding resources sizes refer to the amount of a resource that is visible to a running virtual machine. For the Standard configuration, 1 CPU and 60GB disk space refer to the number of virtual CPUs and the amount of disk space the virtual machine must see. Because virtualization allows many different virtual machines running different operating system instances to share the same physical resources, it's important to size your physical host environment to account for the number of virtual machines you have running.

Memory

In addition to your host environment, it's important to size your physical host to properly account for the amount of memory needed for your running guests. Best practice dictates that your host should have more physical memory than the sum of the memory set up for the simultaneously running guests. For example, if you are trying to size a physical host to run both the Standard and Enhanced configurations, you should pick a host that has 4 + 8 + 2 => at least 14GB or RAM. (The extra 2GB of RAM is recommended for the hypervisor processes).

CPU

When mapping virtual CPUs to physical CPUs you should count one physical CPU core per virtual CPU that will be running simultaneously, and leave at least one core as a buffer for the hypervisor processes. For example, if you are trying to size a physical host to run both the Standard and Enhanced configurations, you should pick a host that has 1 + 2 + 1 = 4 physical CPU cores. Because most physical CPUs are multicore, a physical host with one quad-core CPU is sufficient to run the configurations. Because the App Connect HVE uses a 64-bit kernel, your host must have a physical CPU with virtualization technology support available and enabled, (for example, Intel's VT-x or AMD's AMD-V). In some cases, virtualization technology must be enabled through BIOS.

Disk

Disks are typically the cheapest resource in a virtualized environment. Best practices dictate that a virtual machine should preallocate the amount of disk space required onto physical disks so that performance does not suffer when trying to expand disks later. When sizing disks, you should significantly oversize the disks so you can store many suspended virtual machines at the same time and only instantiate the ones needed. For example, if you are trying to size a physical host to run both the Standard and Enhanced configurations, the minimum requirement for disk space is 60 + 60 + 5 = 125GB. (The remaining 5GB of space is for the hypervisor software). However, best practice is to get a physical host with significantly larger disks so that you can store more inactive virtual machines as your needs grow.




Feedback | Notices


Timestamp icon Last updated: Tuesday, 27 September 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.VAuserguide.doc/VA_resourcemapping.html