Edit On Github

The Deployments Page

---

Deployment Page Reference

When clicking on the Deployments tab and choosing a deployment you will be able to choose one of the following:

Actions Available On A Deployment

The table presented on the deployment page contains a dropdown menu, allowing to perform actions on a deployment. Available actions are: execute workflow, update deployment, and delete.

Execute Workflow

To execute a workflow simply choose the desired workflow name, fill the requested parameters and click Confirm.

Delete Deployment

To delete the deployment, simply click Yes.

Update Deployment

To Update the deployment, simply select or provide a URL to a new archive. If inputs are needed, select an inputs file. If the main blueprint file isn’t named ‘blueprint.yaml’, type a different name. Lastly you can choose whether to run Install and Uninstall workflows on the changes - by default install will run on the added sub-graph and uninstall on the removed sub-graph, but the behavior can be overridden by marking which of the workflows should run, or providing a custom workflow of your own. More details on deployment update can be found at http://docs.getcloudify.org/3.4.0/manager/update-deployment/

Topology

The Topology is an application’s graph of nodes and their relationships, which describes the lifecycle events or other operations that each node and relationship exposes for use in workflows.
Each of the blueprint’s nodes is displayed as a square container, which can contain other nodes. Each node has a title describing its name, and an icon to indicate the node’s type.
Relationships between nodes are marked with arrows, starts from the connected node and ends at the target node.
The topology view shows only the application nodes and not the network nodes. If a node has a network dependency, it will be displayed as a bullet icon in the node’s title.
Host nodes are shown with number bullet beside the node type icon, which indicates the number of instances and number of initiated instances. Contained nodes are shown with status bullet beside the node type icon, which indicates the node status by bullet icon & color. The contained nodes bullet indicates the status of all instances of the specific node. For example, if at least one instance raised an error, the bullet will be colored in red. The bullet color indicates the node current status:

- Node is in loading process
- An error occurred while running the node
- Warning raised while running the node
- Node was initiated successfully

Clicking a node’s title will open a side panel with runtime properties of the selected node. The floating panel allows the user to select which instance details to show.

Network

A map of networks topologies according to the blueprint’s topology contains internal and external networks, hosts, routers.
The network’s name is displayed as a grey title, each network contains sub-networks displayed as colored lines underneath. Network devices, such as hosts & routers, are displayed as icons, each icon indicates the device’s type. Connections between sub-networks and devices are marked with a colored line, by the color of the connected sub-network.
Clicking a device will open a side panel with details of the selected device.

Nodes

A list of nodes according to the blueprint’s topology.
For every node, its type, number of instances, and relationships are shown. By clicking the magnifier icon, a side panel will be opened with the selected node’s details.

Executions

Running instances of a workflow.

Monitoring

See the definition here.