Working with Stacks

Important! The actions that you can perform depend on your folder permissions. See: Assigning Release Automation Permissions.

About Stacks

A Stack is the group of services that make up an application deployed to an Environment. A Stack is a physically running instance of a Blueprint. Depending on the virtualization or cloud provider, a Stack can be mapped to a container or a virtual machine instance of the Stack Template.

A Stack contains all infrastructure/platform layers with the exception of the CDA applications deployed and is provisioned by third-party tools like Docker or VMware vSphere.

Stacks are very useful to deploy multiple services at once without needing to define them one by one.

Viewing Stacks

You can either display a complete list of available Stacks or only the Stacks reachable via a certain Stack Provider.

To View all Stacks Available in the System

1. Click the Provisioning accordion tab.
2. Select Stacks.

To View the Stacks reachable via a Stack Provider

1. Open the Stack Provider.
2. Navigate to General > Stacks.

Tip: For more information about how search for entities and narrow down the results, see Advanced Search.

Changing Properties of Stacks

Properties can be changed:

• From the Stacks sidebar displayed next to the table that lists the Stacks.
• In the Properties section of a Stack.

You can change the following properties:

• General

  Basic attributes of the Blueprint. You can edit the Name, Folder and Owner.

  Notes:

  • GUIDs are used to uniquely identify Stacks. The Stack name consists of the prefix "PROVISIONING_STACK_" and an auto-generated GUID. For example: PROVISIONING_STACK_206426763C469F74AF6A05029DAA919085A.
  • Physical Id: Actual identification string assigned to the Stack. It is used to create or delete Docker containers or VMware machines or to to start/stop or terminate an EC2 instance (AWS).

• Description

  The description is limited to 2000 characters.

• Actions

  Actions are located in the toolbar. They can be also triggered from the context menu displayed after right-clicking the entity. You can trigger the following actions (depending on your permissions):

  • Export: exports the Stack definition in CSV format.
• Statistics & History

Deleting Stacks

Note: Entities provisioned via a Blueprint cannot be deleted independently. This action can only be triggered if the related Environment is deprovisioned.