Skip to main content

​
Overview

Xloud Orchestration manages the complete lifecycle of infrastructure stacks. After initial creation, a stack can be updated with a revised template or new parameter values, suspended to release compute and network resources, resumed when needed, and eventually deleted to clean up all associated resources in a single operation.
Prerequisites

​
Stack Lifecycle

​
Update a Stack

Stack updates apply changes to an existing stack using a revised template or updated parameter values. The engine computes a diff between the current and desired state, then creates, updates, or deletes resources as needed.
Stack updates can cause resource replacement. Resources that do not support in-place updates are deleted and recreated, which may cause downtime. Review the planned changes using --dry-run before applying to production stacks.

Open the stack

Navigate to Project → Orchestration → Stacks and click the stack name to open its detail view.

Edit the stack

Click Edit Stack. The edit wizard opens, pre-populated with the current template and parameter values.

Update the template or parameters

Upload a revised template file or change parameter values, then click Update.
Stack status transitions to Update In Progress, then Update Complete when all changes are applied.

​
Suspend a Stack

Suspending a stack stops all running instances and releases compute resources while preserving the stack definition for later resumption.
In the Stacks list, select the stack and select Suspend Stack from the Actions dropdown.
Stack status transitions to Suspend Complete. Running instances are stopped.

​
Resume a Stack

Resuming a suspended stack restarts all instances and restores the stack to its previous active state.
In the Stacks list, select the suspended stack and select Resume Stack from the Actions dropdown.
Stack status transitions to Resume Complete. Instances return to running state.

​
Stack Outputs

Outputs expose values produced by the stack — IP addresses, resource IDs, URLs, and other runtime data.
Open the stack detail page and select the Outputs tab. All defined outputs and their current values are listed.

​
Nested Stacks

A nested stack is a stack created as a resource within a parent stack using the Xloud::Orchestration::Stack resource type. Nesting enables modular template design — common patterns such as networking tiers, database clusters, or load balancer configurations can be extracted into reusable child templates.
parent-stack-with-nested.yaml
resources:

  network_tier:
    type: Xloud::Orchestration::Stack
    properties:
      template: { get_file: network-template.yaml }
      parameters:
        cidr: "10.0.0.0/24"
        external_network: { get_param: external_network }

  app_tier:
    type: Xloud::Orchestration::Stack
    depends_on: [network_tier]
    properties:
      template: { get_file: app-template.yaml }
      parameters:
        network: { get_attr: [network_tier, outputs, network_id] }
        flavor: { get_param: app_flavor }
Nested stacks appear as child stacks in the Dashboard under the parent stack’s topology view. Each child stack has its own resource list, events, and outputs.

​
Delete a Stack

Deleting a stack permanently destroys all resources it manages — including instances, volumes marked for deletion, networks, and floating IPs. Resources with deletion_policy: Retain in the template are preserved.
In the Stacks list, select the stack and click Delete Stacks. Confirm the operation in the confirmation dialog.
Stack transitions to Delete In Progress and then disappears from the list.

​
Next Steps

Auto-Scaling

Create auto-scaling groups and alarm-driven scaling policies

Template Guide

Author templates with parameters, conditions, and intrinsic functions

Resource Types

Full reference for all supported resource types and their properties

Troubleshooting

Resolve stack update failures, rollback issues, and dependency errors