Making classic virtual system patterns read-only

You can deploy both draft and read-only classic virtual system patterns for testing or production.

Before you begin

You must have edit access to the classic virtual system pattern that you want to make read-only. If the pattern is read-only already, you cannot change it. To make a classic virtual system pattern read-only, ensure that no one with the permission to edit the classic virtual system pattern intends to change it.

Making a classic virtual system pattern read-only prevents further edits to the topology definition and ensures consistent reuse in the cloud.

About this task

You can make classic virtual system patterns read-only to prevent further editing of the classic virtual system pattern.
Note: When you make a classic virtual system pattern read-only, it is possible for the pattern to contain script packages or add-ons that are still in draft state (that is, unlocked). The pattern model is unchanged, but it is still possible to modify the script package or add-on if it is not also locked.

Procedure

  1. Click Patterns > Virtual System Patterns (Classic).
  2. Select the classic virtual system pattern.
    Classic virtual system patterns that have the read-only symbol cannot be edited. Classic virtual system patterns with the edit symbol beside them can be edited.
  3. To lock editing of the classic virtual system pattern, click the Lock icon in the toolbar of the Patterns window.
  4. When prompted, click OK to lock the classic virtual system pattern.

Results

The classic virtual system pattern is now read-only.
Note: For version 1.1.0.2 and later, if the pattern contains one or more script packages or add-ons that are not locked, the Current status field in the Virtual System Patterns details page is displayed with the following status:
Read-only (The pattern content can still be modified because some script packages or add-ons are not read-only)

You can lock your script packages and add-ons as needed before deploying the virtual system pattern. Return to the appropriate catalog page in the console to select the appropriate script package or add-on and use the Lock function to change the state to read-only.

What to do next

You can deploy the classic virtual system pattern to the cloud. For more information, see the related links.