Managing System Resources

The appearance of this page depends on your permissions. Only an admin can view information about snapshots.


By default, plugins are tenant-specific, meaning that a blueprint on one tenant cannot access a plugin on a different tenant. You can also set a plugin as global when you upload it to the manager. The Plugins table lists the plugins are available to the current tenant.

Uploading a Plugin

  1. Click Upload above the Plugins table.
  2. Either enter the URL of the wagon or select the wagon file from your file repository.
  3. Either enter the URL of the plugin yaml file or select the plugin yaml file from your file repository.
  4. Click Upload.
    The plugin details appear in the Plugins table.


The Snapshots table provides a list of all snapshots that have been uploaded or created. The Snapshots table is only available if you have admin credentials.

The snapshots creation process captures data in the entire Cloudify Manager, not just that of a specific tenant. However, the snapshot is created in the context of the current tenant, and therefore must be restored from it. Snapshots are created as a private resource by default and it cannot change.

Creating a Snapshot

  1. Click Create above the Snapshots table.
  2. Specify a unique ID for the snapshot and click Create.
    It is good practice to use a name that will help you to easily identify the snapshot later.

The creation process begins. If there are active executions when you attempt to create the snapshot, the process waits until the executions are complete before creating the snapshot. You can see the status of executions in the Deployment executions widget.

The snapshot is saved as a ZIP file and appears in the Snapshots table, together with details of its creator, creation date and time, and current status.

Restoring a Snapshot

If you are restoring a snapshot from a Cloudify Manager instance prior to version 4.0, refer to the Restoring Snapshots of Legacy Cloudify Manager Instances section below.

If you restore a snapshot to a Cloudify Manager instance that already contains data, that data is overwritten. To prevent inadvertent overwriting of existing data, you must explicity state that you want to force data overwrite.

  1. Click Upload in the Snapshots widget.
  2. Either enter the URL of the snapshot or select the snapshot file from your file repository.
  3. Enter the Snapshot ID.
  4. Click Upload.
  5. To restore a snapshot from a tenant-less (legacy) environment, toggle the relevant button.

  6. The snapshot is restored and its details appear in the Snapshots table.

Restoring Snapshots of Legacy Cloudify Manager Instances

This subsection refers to the process for restoring snapshots of Cloudify Manager instances that were created prior to Cloudify Mananger 4.0.

If you are restoring a snapshot from an older, tenant-less (legacy) version of Cloudify to Cloudify Manager, it will be restored in a specific tenant that you must provide. The process enables you to migrate one or more legacy Cloudify Manager instances to a version 4.X instance, and to keep their resources separate.

To enable a snapshot to be successfully installed on a Manager, you must specify the name of a tenant. Depending on your requirements, the tenant may be prepared according to one of the following options. It is recommended that you select the first option, to ensure optimal performance of your plugins.

Deleting a Snapshot

  1. In the Snapshots widget, click icon_trash_grey for the snapshot entry that you want to delete.
  2. Click Yes to delete the snapshot from Cloudify Manager.

Working with Secrets

Secret storage provides a tenant-wide variable store for data that you do not want to expose in plain text in Cloudify blueprints, such as login credentials for a platform. For more information about secret storage, [click here](/about/manager_architecture/security/(#additional-security-information).