Implementing a Virtual Server Environment: Getting Started
Table Of Contents
- Chapter 1: Introduction
- Chapter 2: Assessing and Planning
- Chapter 3: Understanding the Choices for Virtualization Technologies
- Partitioning Solutions:
- Why choose nPartitions (nPars)?
- Why choose Virtual Partitions (vPars)?
- Why choose Integrity Virtual Machines (VMs)?
- Why choose Resource Partitions or Secure Resource Partitions (SRPs)?
- HP Utility Pricing Solutions:
- Why choose Instant Capacity (iCAP)?
- Why choose Temporary Instant Capacity (TiCAP)?
- Why choose Global Instant Capacity (GiCAP)
- Automation Solutions:
- Why choose Global Workload Manager (gWLM) or Workload Manager (WLM)?
- Chapter 4: HP VSE Reference Architectures
- Chapter 5: Identifying a Pilot Project
- Chapter 6: Making Your Choices
- For more information
• Operating system isolation (each vPar is a unique instance of HP-UX).
• CPU and memory resources can be changed or moved dynamically between vPars that are
within the same nPar.
• Negligible overhead
• Good choice for I/O-intensive applications as compared with HP Integrity Virtual Machines.
Trade-offs
• No hardware fault isolation for vPars running in the same nPar (that is, a hardware failure
within an nPar will affect all vPars in that nPar).
• HP-UX is the only operating system supported.
• Only supported on cell-based systems if using Integrity servers (some older, non-cell-based
systems are supported on PA-RISC).
• Requires dedicated hardware resources, which might result in overprovisioning for small
workloads.
Sweet Spots
• A good choice if you require finer granularity than an nPar but still need dedicated
hardware, have I/O-intensive applications, or need a unique instance or version of HP-UX.
• A good choice if you want to dynamically move processor or memory resources between
vPars (within the same nPar).
• Instant Capacity or Temporary Instant Capacity resources can be activated for any vPar
within the same nPar.
• Easy for deploying a new application or a new instance of an existing application by simply
creating a new vPar (instead of deploying a new server).
• Different versions of HP-UX (e.g. 11iv1, 11iv2, and 11iv3) can run in separate vPars within
the same nPar.
Why choose Integrity Virtual Machines (VMs)?
Key Benefits
• Granularity is sub-CPU (as little as 5%).
• Virtual CPUs (vCPUs), CPU entitlements, and memory can be changed dynamically.
• Dedicated hardware not required; CPU and I/O resources are shared.
• Supported on all Integrity systems (running HP-UX 11i v2 or later) and on both cell-based and
non-cell-based servers, including Integrity server blades.
• Operating system isolation and flexibility (that is, each guest OS is a unique instance).
• Multiple OS guests are supported (HP-UX, Windows, and Linux; OpenVMS is planned).
• OS guests can run without modification.
• Any virtual storage device (disk, CD, DVD) can be implemented as a file.
• An ISO image of a preferred software image can be implemented as a virtual DVD, and can
be used to quickly deploy common software, operating system updates, or patch bundles to
multiple virtual machines.
• Starting with the 4.1 version, they can be migrated online from one host to another.
Trade-offs
• No hardware fault isolation.
7