You deploy a classic virtual system pattern by selecting an environment profile
and then specifying cloud group or groups
for deployment. Make your selections from the following options:
- IP version
- Click one of the IP version options (IPv4 or IPv6).
- Choose profile
- Select this option to deploy the classic virtual system pattern by using an environment profile. Then
select the environment Type and a valid environment
Profile from the lists. You can also set a
Priority (High, Medium, or Low).
Important: If the
Pattern deployer option was chosen, you cannot specify an IP address that is
contained within the IP groups that are
defined in the system.
Note: Classic virtual system patterns cannot be deployed to multi-cloud environment profiles or cloud
groups.
For more information about administering environment profiles, see the related
links.
For each virtual image part that requires information, click the link and provide the
information for each configuration parameter shown. The set of parameters depends on the type of
part. The parts that require information are different depending on the type of virtual image to be
deployed and the type of hypervisors in the cloud. For example, parts for a WebSphere® Application Server image would require different information than parts for a DB2® image.
Note: Do not
use the
root user as the WebSphere
administrative user name.
When specifying values for DB2 parameters, be aware that owner and user group names, as well as instance owner names, fenced user names, and DB2 administration server (DAS) user names can only have up to 8 characters.
If the information for each of the virtual image parts is complete, a green
check mark is shown next to the virtual image part. If some information is missing, the check box
does not contain a green check mark. If so, you must provide the required information.
If you
are using an environment profile there might be additional fields to configure for the parts. If the
environment profile specifies that the classic virtual system pattern deployer is to provide the IP
address, the IP addresses must also be provided for the parts.
Specify the following part
information:
- In cloud group
- Select the cloud group. If an alias was provided to define the cloud group in the environment
profile, then the alias name is available to be selected in this field.
Restriction: If
you deploy the virtual images to differing cloud groups, then you cannot use the system monitoring
service to monitor all of the virtual machines. System monitoring is supported only for deployments
to single cloud groups.
- IP Group
- Select an IP group. If an alias was
provided to define the IP group in the
environment profile, then the alias name is available to be selected in this field.
- Addresses
- Provide both the host name and the IP address. The host name and IP address must not exist in
the selected IP group.
If you are deploying parts with add-ons, you can configure fields for those add-ons if
they were not configured when the part was created and locked to editing during deployment.
If
there is a
Default attach block disk add-on in the pattern, select an
existing volume for the
Volume_ID field, or click
Create to create a volume and attach it to the component during deployment.
If you choose to create a new volume, configure these settings:
- Name
- Set the name for the volume.
- Description
- Optional. Set a description for the volume.
- Size (GB)
- Set the size for the volume, in GB.
- Volume Groups
- Select a volume group for the volume. A volume group is a logical grouping of volumes that can
span workloads and cloud groups.