 |
» |
|
|
|
The HP Instant Capacity (iCAP) and HP Pay per use (PPU) software
products are a part of the HP Utility Pricing Solutions program.
iCAP is a purchase model in which capacity can be instantly increased
to accommodate increasing demands. PPU is a lease model in which
customers are charged only for actual processor usage. HP
Instant Capacity | |
The HP Instant Capacity (iCAP) version B.11.23.08.00.xx software (product number B9073BA) provides the ability
to instantly increase or decrease processing capacity on specified
HP Enterprise servers. HP Instant Capacity (iCAP) has been updated to version B.11.23.08.00.xx with the following changes and enhancements: HP Instant Capacity now includes support
for Global Instant Capacity, or GiCAP, which provides HP customers
with the flexibility to move usage rights for Instant Capacity components
within a group of servers, and it also provides “pooled” temporary
capacity across the group. Instant Capacity now includes support for the rx7640
and rx8640 servers. The commands icapmodify -d, icapmodify -a, and icapmodify -s (formerly icod_modify) have been enhanced so they will work on systems that
do not contain Instant Capacity components. This allows you to test
the use of Instant Capacity, and it allows non-Instant Capacity
systems to participate in a GiCAP group and share usage rights. Changes have been made to Instant Capacity command
names, terminology, files, and messages, including: “Instant
Capacity on Demand,” or “iCOD,” is changed to
“Instant Capacity,” or “iCAP.” The terms “processor” and
“CPU” are changed to “core” to be more
accurate with the new generation hardware. References to “licensed” and
“unlicensed” are changed to refer to “usage rights” or
“without usage rights” to be more aligned with the “Right
to Use” (RTU) terminology. References to “iCOD
component” are changed to reflect the reality that on an Instant
Capacity system, individual components are not identified as iCAP,
but instead the software tracks the number of components which must
be inactive due to a lack of usage tights. Instant Capacity command names are changed as follows: icod_stat becomes icapstatus icod_modify becomes icapmodify icod_notify becomes icapnotify
The new command icapmanage provides management commands for Global Instant Capacity. The manpages are also renamed to reflect the command
changes: The output of the icapstatus command (formerly icod_stat) has been changed to reflect the new terminology and
to incorporate several new features: A more concise
description of Instant Capacity resources among the partitions (condensed
to one section instead of two) Additional line item for
the number of inactive cores on the local hard partition The line item that previously
displayed “Processors that can be activated if licensed” is
now expanded to two items, showing “Additional cores that
can be activated with temporary capacity” and “Number
of cores that could be activated with additional usage rights” If the server participates
in a GiCAP group, some information about the group and about borrowed
or loaned usage rights is included
Various additional filename changes have been made:
The Instant Capacity daemon name is changed to icapd (formerly icodd). The Instant Capacity log file is changed to /var/adm/icap.log (formerly icod.log). The documentation files are changed to /usr/share/doc/icapReleaseNotes.pdf and /usr/share/doc/icapUserGuide.pdf. A new file, /usr/share/doc/icapOverview.htm can be used to link to the most up-to-date documentation
files on the HP Web site. In particular, if you do not have a pdf reader,
this allows you to link to the html versions of the documents on
the Web site. On systems which do not contain Instant Capacity
components, icapstatus gives detailed information about the system instead of
the abbreviated information previously reported. The icapstatus command now displays the new system product number rather than
the original product number if a system is upgraded from one hardware version
to another.
On HP-UX 11i v2, HP Instant Capacity (iCAP) version B.11.23.08.00.xx supersedes HP Instant Capacity version B.11.23.07.00. Additional HP-UX patches may be required. See the HP
Instant Capacity Release Notes at http://docs.hp.com/en/netsys.html for further information. HP Instant Capacity now includes support for Global Instant
Capacity, or GiCAP, which provides HP customers with the flexibility
to move usage rights for Instant Capacity components within a group
of servers, and it also provides “pooled” temporary
capacity across the group. This has several potential benefits:
cost-effective high availability, more adaptable load balancing,
and more efficient and easier use of temporary capacity. Note that
in order to manage the GiCAP group, a new command icapmanage is provided. For example, in case of planned or unplanned downtime, a customer
can transfer usage rights (RTUs) from a failed partition on one
server to one or more other servers in the group that are providing
backup availability, thus allowing additional activations of iCAP
components on the backup servers. Without GiCAP, the only way to
provide this failover scenario is to provision each server with
an adequate amount of temporary capacity in case of potential failures. A similar scenario exists for load balancing. Rather than
using temporary capacity whenever a server is overloaded (peak profiles
for all workloads on a server), usage rights (RTUs) can be transferred
from other servers in the GiCAP group that have extra capacity,
enabling new activations for the overloaded system. Previous command names such as icod_stat, icod_modify, and icod_notify still work, but are now just filenames symbolically linked
to the new command names. References to the old command names will
see the new terminology as detailed above. You may also reference the older manpages such as man icod, but these references give the exact same output as the
new man commands. All manpage references use the new terminology
as detailed above. A filename called /var/adm/icod.log is symbolically linked to the new log filename /var/adm/icap.log so that you may still reference the previous filename. While the size of GiCAP groups is not specifically restricted,
performance of group-related functions is affected by the number
of group members and the number of partitions for each member server,
as well as the types of hardware involved. For further information, see the following: Documents: For details on the HP Instant Capacity software product, see
the Instant Capacity User’s Guide and Release
Notes located on the HP Web site http://docs.hp.com (under Network and Systems
Management -> Utility
Pricing Solutions)
The previous commands of icod_stat, icod_notify, and icod_modify are now deprecated; users can still invoke these commands
but they are symbolically linked to the new commands of icodstatus, icodnotify, and icodmodify, respectively. The icodd daemon has been replaced by the icapd daemon. HP
Pay per use | |
The HP Pay per use (PPU) program is a lease model in which
customers are charged only for the computing capacity that they
use. The PPU software (HP product T2351AA) provides services for
metering resource utilization. PPU has been updated to version B.11.23.08.00.xx with the following changes: PPU now includes
support for the rx7640 and rx8640 servers. To more accurately represent
the new generation of hardware, all references to “processor” and
“CPU” have been changed to “core.” The
two metrics for measuring and pricing utilization are now called
Percent Core and Active Core (previously known as Percent CPU or
Processor Percent, and Active CPU or Number Active Processors). PPU can be run in an HP Integrity
Virtual Machines environment (HPVM). In this case, the usage information
for billing purposes is still the overall usage for the host. However,
you can examine the usage report at the portal to see a detailed
breakdown of the usage for each Virtual Machine (also called a “guest”).
In an HPVM environment, PPU needs to be installed and configured
only on the host, not on the guest Virtual Machines. The command ppuconfig -t has been enhanced to do additional validation of configuration
and environment and will also restart the ppud daemon if it is not already started. Previously, when a cell contained
dual-core processors and was powered down (inactive), then PPU on
another partition of the complex would report the number of cores
for the inactive cell as if it contained single-core processors.
Now, as long as there is at least one cell that is powered up in
the same partition as the inactive cell, then PPU will correctly
report the number of cores. If there are no active cells in the partition,
then PPU must make an assumption about the number of cores and by default
will assume single-core processors when reporting TotalCores for
the complex. The error messages and manpages
have been enhanced and updated. A new documentation file,
/usr/share/doc/PayPerUseOverview.htm, is provided to link to the most current documentation
files on the HP documentation Web site. In particular, if you do
not have a pdf reader, you can use this file to link to the Web site
where html-formatted files exist.
PPU Version B.11.23.08.00.xx supersedes version B.11.23.07.02 on HP-UX 11i v2. The two metrics for measuring pricing and utilization are
now called Percent Core and Active Core (previously known as Percent
CPU or Processor Percent, and Active CPU or Number Active Processors).
The billing amounts vary as your core usage increases or decreases.
This is different than traditional financing approaches that are
based on fixed-payment amounts for a specified period. PPU can be
run in an HP Integrity Virtual Machines environment (HPVM). In this
case, the usage information for billing purposes is still the overall
usage for the host. However, you can examine the usage report at
the portal to see a detailed breakdown of the usage for each Virtual
Machine (also called a “guest”). In an HPVM environment,
PPU needs to be installed and configured only on the host, not on
the guest Virtual Machines. (PPU commands are therefore only executed on
the host). While the utilization metric names have changed, as well as
other terminology, the methods of measuring resource utilization
have not changed. There are no known compatibility issues. There are no known performance issues. For further information, see the following: Manpages: ppu(5) ppuconfig(1M) ppud(1M) Documents: For details on the Pay per use software product, see the Pay
per use User’s Guide and Release
Notes located on the HP Web site http://docs.hp.com (under Network and Systems Management -> Utility
Pricing Solutions).
|
Printable version
