Operating Environment Software Instruction Manual

NOTE: When infrastructure orchestration is upgraded to a new version, administrator modifications
to individual properties in hpio.properties are migrated to the new version of the file unless
the default value of the property changed in the new version. In that case, the value of the property
is overwritten by the new default value included in hpio.properties.
For example, in an earlier version of infrastructure orchestration, the value of
timeout.get.vmhost was 4 minutes, and in a later version, the default value is 10 minutes.
If, in the earlier version of the file, the administrator set the value to 12 minutes, this value is
overwritten in the later version by the new value of 10 minutes.
In general, administrator changes to hpio.properties require the HP Matrix infrastructure
orchestration Windows service to be restarted. The properties that do not require a restart are:
• Default OS customization file: os.customization.default.file
• OS customization directory: os.customization.directory
• Template access restrictions: template.access.restricted
• Telnet console enablement: display.telnet.console.link
• Single-server services hostname suffix:
single.server.services.have.hostname.suffix
• Global pattern for hostname suffixes: hostname.suffix.pattern
The preceding are hpio.properties entries that infrastructure orchestration self service portal,
organization administrator portal, designer, and console read directly.
Configuring a federated CMS environment
A Matrix infrastructure orchestration federated CMS environment is an environment in which multiple
management servers cooperatively share the responsibility for managing a larger number of
resources than can be managed by a single server.
A new infrastructure orchestration installation is configured as a primary CMS, and is ready to
control a federated CMS environment when secondary CMSs are installed and configured.
An infrastructure orchestration federated CMS environment:
• allows increased scalability for service catalog-based auto-provisioning (up to 12,000 ProLiant
virtual machines and 6,000 HP Integrity virtual machines)
• contains one primary CMS running infrastructure orchestration, and one or more secondary
CMSs running Matrix Operating Environment (infrastructure orchestration cannot be installed
on secondary CMSs)
A federation can contain up to five CMSs. The recommended configuration is:
• one primary CMS with up to 1200 managed nodes
• up to four secondary CMSs with up to 2200 managed nodes each
The primary CMS manages the aggregated resources of all CMSs. Matrix infrastructure orchestration
must be installed only on this server. A secondary CMS is a CMS that participates in the federation,
where resources exist and provisioning from infrastructure orchestration may occur, but infrastructure
orchestration does not run directly on secondary CMSs.
To execute infrastructure orchestration provisioning across multiple CMSs, infrastructure orchestration
on the primary CMS uses the secondary CMSs logical server management, virtual machine
management, and other supporting software layers.
For more information, see the HP Matrix Operating Environment Federated CMS Overview white
paper at Matrix Operating Environment Information Library.
Configuring a federated CMS environment 19