HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

NOTE: Trunk networks (mapped or tunnel) cannot be customized. A trunk network configured in
a service template cannot be replaced with another network, nor can a trunk network be used to
replace another network.
If you specify a network by selecting “Specify desired attributes”, you cannot customize the network
when the service is created. Network customization can be performed only on named networks.
Customizations affect only the service being created. The template is not changed.
Organization administrators and users can customize networks only that are accessible to the
organization.
Clicking to select the Customizable check box in the template in infrastructure orchestration designer
allows the IO architect to specify that the template may be customized.
When you create a service from the template in infrastructure orchestration console, organization
administrator portal, or self service portal, you specify the custom attributes on the Create Service
Options dialog. These attributes must take the following form:
subnet=<network-name-in-template>,<replacement-network-name>
addressingType=<logical-server-group-name>,<network-name>,DHCP |
AUTOMATIC | STATIC [,<IP address>...]
memory=<logical-server-group-name>,<new-size>MB | GB
processor=<logical-server-group-name>,<new-count>.
A tooltip is displayed containing the required format when you click the Custom Attributes text
box. The text box expands in size when the cursor is placed in it, and is greyed out if the template
is not customizable.
For example, to change the network name to “replacement network”, the network assignment type
to “static”, the IP address to 192.168.0.99, the amount of memory to 4GB, and number of
processors to 2, enter:
subnet=network-in-my-template, replacement-network;
addressingType=server-group-in-my-template,
second-network-in-my-template,STATIC,192.168.0.99;
memory=server-group-in-my-template,4GB;
processor=server-group-in-my-template,2
Creating a service request 129