Resource Types

Overview

Polystack Orchestration supports over 100 built-in resource types covering the full range of cloud infrastructure. Each resource type maps to a specific cloud service API. The Orchestration engine provisions resources in dependency order and tracks their lifecycle as part of the parent stack.

Resource type names use the Polystack::Service::ResourceType convention. Available resource types depend on the services enabled in your cluster.

Resource Categories

Category	Service	Common Resource Types
Compute	Polystack Compute	Server, KeyPair, ServerGroup
Networking	Polystack Networking	Net, Subnet, Router, RouterInterface, FloatingIP, SecurityGroup, Port
Storage	Polystack Block Storage	Volume, VolumeAttachment
Identity	Polystack Identity	Project, User, Role
Orchestration	Polystack Orchestration	Stack, WaitCondition, AutoScalingGroup, ScalingPolicy

Resource Definition Structure

Every resource follows this structure:

resource-structure.yaml

resources:
  logical_resource_name:
    type: Polystack::Service::ResourceType    # Required
    depends_on:                           # Optional — explicit ordering
      - other_resource_name
    condition: my_condition               # Optional — conditional creation
    deletion_policy: Delete               # Optional — Retain | Snapshot | Delete
    properties:                           # Required — resource configuration
      property_name: value
      property_from_param: { get_param: param_name }
      property_from_resource: { get_resource: other_resource }
    metadata:                             # Optional — arbitrary key-value data
      custom_key: custom_value

`depends_on` and Dependency Resolution

The engine automatically detects dependencies from intrinsic functions like get_resource and get_attr. Use depends_on only for ordering requirements that cannot be expressed through property references.

explicit-dependency.yaml

resources:
  network:
    type: Polystack::Networking::Net
    properties:
      name: app-network

  subnet:
    type: Polystack::Networking::Subnet
    depends_on: [network]               # Wait for network before creating subnet
    properties:
      network_id: { get_resource: network }
      cidr: "10.0.1.0/24"

Resource Examples by Category

Compute Resources

Polystack::Compute::Server

compute-server.yaml

resources:
  web_server:
    type: Polystack::Compute::Server
    properties:
      name: web-server
      image: { get_param: image }
      flavor: { get_param: flavor }
      key_name: { get_param: key_name }
      security_groups:
        - { get_resource: web_sg }
      networks:
        - network: { get_param: network }
      user_data_format: RAW
      user_data: |
        #!/bin/bash
        apt-get install -y nginx
        systemctl enable --now nginx

Polystack::Compute::KeyPair

keypair.yaml

resources:
  deploy_key:
    type: Polystack::Compute::KeyPair
    properties:
      name: deploy-key
      save_private_key: true   # Private key returned as stack output

outputs:
  private_key:
    value: { get_attr: [deploy_key, private_key] }

Polystack::Compute::ServerGroup

server-group.yaml

resources:
  anti_affinity_group:
    type: Polystack::Compute::ServerGroup
    properties:
      name: web-anti-affinity
      policies:
        - anti-affinity     # Spread instances across different hosts

Networking Resources

Polystack::Networking::Net

network.yaml

resources:
  app_network:
    type: Polystack::Networking::Net
    properties:
      name: app-network
      admin_state_up: true

Polystack::Networking::Subnet

subnet.yaml

resources:
  app_subnet:
    type: Polystack::Networking::Subnet
    properties:
      name: app-subnet
      network_id: { get_resource: app_network }
      cidr: "192.168.10.0/24"
      ip_version: 4
      dns_nameservers:
        - "8.8.8.8"
        - "1.1.1.1"
      enable_dhcp: true

Polystack::Networking::Router and RouterInterface

router.yaml

resources:
  router:
    type: Polystack::Networking::Router
    properties:
      name: app-router
      external_gateway_info:
        network: { get_param: external_network }

  router_interface:
    type: Polystack::Networking::RouterInterface
    properties:
      router_id: { get_resource: router }
      subnet_id: { get_resource: app_subnet }

Polystack::Networking::FloatingIP

floating-ip.yaml

resources:
  floating_ip:
    type: Polystack::Networking::FloatingIP
    properties:
      floating_network: { get_param: external_network }

  floating_ip_assoc:
    type: Polystack::Networking::FloatingIPAssociation
    properties:
      floatingip_id: { get_resource: floating_ip }
      port_id: { get_attr: [web_server, addresses, app-network, 0, port] }

Polystack::Networking::SecurityGroup

security-group.yaml

resources:
  web_sg:
    type: Polystack::Networking::SecurityGroup
    properties:
      name: web-security-group
      description: Allow HTTP, HTTPS, and SSH
      rules:
        - protocol: tcp
          port_range_min: 22
          port_range_max: 22
          remote_ip_prefix: "0.0.0.0/0"
        - protocol: tcp
          port_range_min: 80
          port_range_max: 80
          remote_ip_prefix: "0.0.0.0/0"
        - protocol: tcp
          port_range_min: 443
          port_range_max: 443
          remote_ip_prefix: "0.0.0.0/0"

Storage Resources

Polystack::BlockStorage::Volume

volume.yaml

resources:
  data_volume:
    type: Polystack::BlockStorage::Volume
    properties:
      name: app-data
      size: 100          # GB
      volume_type: ceph-ssd
      description: Application data volume

Polystack::BlockStorage::VolumeAttachment

volume-attachment.yaml

resources:
  data_volume_attach:
    type: Polystack::BlockStorage::VolumeAttachment
    properties:
      instance_uuid: { get_resource: web_server }
      volume_id: { get_resource: data_volume }
      mountpoint: /dev/vdb

Identity Resources

Polystack::Identity::Project

project.yaml

resources:
  app_project:
    type: Polystack::Identity::Project
    properties:
      name: my-app-project
      description: Project for the application team
      enabled: true

Polystack::Identity::User

user.yaml

resources:
  svc_user:
    type: Polystack::Identity::User
    properties:
      name: svc-deployer
      password: { get_param: svc_password }
      email: svc-deployer@example.com
      enabled: true

Orchestration Resources

Polystack::Orchestration::Stack (Nested Stack)

nested-stack.yaml

resources:
  database_tier:
    type: Polystack::Orchestration::Stack
    properties:
      template: { get_file: database-stack.yaml }
      parameters:
        flavor: { get_param: db_flavor }
        network: { get_resource: app_network }

Polystack::Orchestration::WaitCondition

Use WaitCondition to pause stack creation until an external signal is received (e.g., after cloud-init completes application installation):

wait-condition.yaml

resources:
  wait_handle:
    type: Polystack::Orchestration::WaitConditionHandle

  app_ready:
    type: Polystack::Orchestration::WaitCondition
    depends_on: [app_server]
    properties:
      handle: { get_resource: wait_handle }
      timeout: 300          # Seconds to wait for signal
      count: 1

  app_server:
    type: Polystack::Compute::Server
    properties:
      user_data:
        str_replace:
          template: |
            #!/bin/bash
            apt-get install -y myapp
            # Signal completion
            curl -X POST "$WAIT_URL" -d '{"Status": "SUCCESS", "UniqueId": "app"}'
          params:
            $WAIT_URL: { get_resource: wait_handle }

Next Steps

Template Guide

Template structure, parameters, intrinsic functions, and conditions

Auto-Scaling

Auto-scaling group and scaling policy resource examples

Manage Stacks

Create, update, and manage the stack lifecycle

Troubleshooting

Diagnose resource provisioning failures and dependency errors

Core Services

Other Services

Overview

Resource Categories

Resource Definition Structure

`depends_on` and Dependency Resolution

Resource Examples by Category

Polystack::Compute::Server

Polystack::Compute::KeyPair

Polystack::Compute::ServerGroup

Polystack::Networking::Net

Polystack::Networking::Subnet

Polystack::Networking::Router and RouterInterface

Polystack::Networking::FloatingIP

Polystack::Networking::SecurityGroup

Polystack::BlockStorage::Volume

Polystack::BlockStorage::VolumeAttachment

Polystack::Identity::Project

Polystack::Identity::User

Polystack::Orchestration::Stack (Nested Stack)

Polystack::Orchestration::WaitCondition

Next Steps

Template Guide

Auto-Scaling

Manage Stacks

Troubleshooting

​Overview

​Resource Categories

​Resource Definition Structure

​depends_on and Dependency Resolution

​Resource Examples by Category

​Polystack::Compute::Server

​Polystack::Compute::KeyPair

​Polystack::Compute::ServerGroup

​Polystack::Networking::Net

​Polystack::Networking::Subnet

​Polystack::Networking::Router and RouterInterface

​Polystack::Networking::FloatingIP

​Polystack::Networking::SecurityGroup

​Polystack::BlockStorage::Volume

​Polystack::BlockStorage::VolumeAttachment

​Polystack::Identity::Project

​Polystack::Identity::User

​Polystack::Orchestration::Stack (Nested Stack)

​Polystack::Orchestration::WaitCondition

​Next Steps

Template Guide

Auto-Scaling

Manage Stacks

Troubleshooting

Overview

Resource Categories

Resource Definition Structure

`depends_on` and Dependency Resolution

Resource Examples by Category

Polystack::Compute::Server

Polystack::Compute::KeyPair

Polystack::Compute::ServerGroup

Polystack::Networking::Net

Polystack::Networking::Subnet

Polystack::Networking::Router and RouterInterface

Polystack::Networking::FloatingIP

Polystack::Networking::SecurityGroup

Polystack::BlockStorage::Volume

Polystack::BlockStorage::VolumeAttachment

Polystack::Identity::Project

Polystack::Identity::User

Polystack::Orchestration::Stack (Nested Stack)

Polystack::Orchestration::WaitCondition

Next Steps