Cloning classic virtual system patterns

You can clone an existing classic virtual system pattern and then customize the copy for your environment.

Before you begin

Note: The Virtual System Patterns (Classic) is not supported in IBM Cloud Pak SystemSoftware version 2.3.5 and later.
Select a classic virtual system pattern that most closely meets your needs. For classic virtual system pattern descriptions, see the related links.
Because classic virtual system patterns are associated with virtual images, you must accept the license agreement for the virtual image associated with the classic virtual system patterns. If you do not accept the license agreement, you cannot clone the classic virtual system patterns. To accept the license, click Catalog > Virtual Images and locate the image associated with the classic virtual system pattern. For more information about working with virtual images, see the related links.
Important: You can accept a license and then change the image that the classic virtual system pattern is using when you define the cloned classic virtual system pattern. If you change the image but you do not use the image for which you accepted the license, you are not charged for that license.

Similarly, script packages that are included in your classic virtual system pattern might have one or more license agreements that you must accept before you can clone the pattern. For more information, see the related links.

Procedure

  1. Click Patterns > Virtual System Patterns (Classic).
  2. Select a classic virtual system pattern.
  3. Click the Clone icon in the toolbar.
  4. Provide the following information about the new classic virtual system pattern:
    Name
    Enter a unique name for the classic virtual system pattern in the Name field.
    Description
    (Optional) Enter a detailed description to identify the classic virtual system pattern.
    Virtual image
    From the list, select a virtual image with which to associate the classic virtual system pattern. You can edit the new classic virtual system pattern to associate individual parts with different virtual images.

    Use this option if all the parts in the classic virtual system pattern you are cloning are from a single virtual image. This option switches all of the parts to a different virtual image in the new classic virtual system pattern.

    If the original classic virtual system pattern contains parts from different virtual images, this option is disabled. In this case, the parts in the new classic virtual system pattern are associated with the same virtual images as the corresponding parts in the original classic virtual system pattern.

  5. Click OK.
    When the information is processed, the Virtual System Pattern pane displays. The classic virtual system pattern that you created is added to the list. It is selected so that the information about it is shown on the right. For more information about the fields on this panel, see the related links.
  6. Edit the classic virtual system pattern.
    To change the classic virtual system pattern topology, click the edit icon. You can perform the following actions with classic virtual system patterns:
    • Add or remove parts.
    • Edit parts.
    • Add or remove script packages to the parts.
    • Add or remove add-ons to the parts.
    • Configure properties for the parts and parameters for the script packages that have parameters.
    • Define advanced options.
    • Modify the startup order of the parts.
    The Pattern Editor window provides a list of parts. For more information about the parts, see the related links.
  7. Edit the parts on the canvas.
    For more information about modifying classic virtual system patterns, see the related links.
  8. Configure advanced options.
    For more information about configuring advanced options, see the related links.
  9. Click Done editing.

Results

You can now customize the copy of the classic virtual system pattern that you created.

What to do next

You can lock the classic virtual system pattern against future editing. For more information about making classic virtual system patterns read-only, see the related links. You can also deploy the classic virtual system pattern to the cloud. For more information about deploying, see the related links.