OpenStack Tools
EEM tools for OpenStack: compute instances, networks, volumes, images, keypairs, routers, floating IPs, and Heat orchestration stacks. Identifiers use snake_case (openstack_server_list) and route through the standard approval flow on destructive verbs.
Tools
Compute
openstack_server_list, List servers in a projectopenstack_server_show, Show server detailsopenstack_server_create, Launch a new serveropenstack_server_delete, Delete a serveropenstack_server_start, Start a stopped serveropenstack_server_stop, Stop a running serveropenstack_server_reboot, Reboot a serveropenstack_server_resize, Resize a server to a new flavoropenstack_flavor_list, List available flavorsopenstack_flavor_show, Show flavor detailsopenstack_keypair_list, List SSH keypairsopenstack_keypair_create, Create an SSH keypairopenstack_keypair_delete, Delete an SSH keypair
Networking
openstack_network_list, List networksopenstack_subnet_list, List subnetsopenstack_security_group_list, List security groupsopenstack_router_list, List routersopenstack_router_create, Create a routeropenstack_router_delete, Delete a routeropenstack_floatingip_create, Allocate a floating IPopenstack_floatingip_delete, Release a floating IP
Block Storage
openstack_volume_list, List volumesopenstack_volume_create, Create a volumeopenstack_volume_delete, Delete a volumeopenstack_volume_attach, Attach a volume to a serveropenstack_volume_extend, Extend a volume's sizeopenstack_volume_snapshot_create, Create a volume snapshotopenstack_volume_snapshot_list, List volume snapshots
Images
openstack_image_list, List imagesopenstack_image_upload, Upload a new imageopenstack_image_delete, Delete an image
Orchestration (Heat)
openstack_stack_list, List Heat stacksopenstack_stack_show, Show a Heat stackopenstack_stack_create, Create a Heat stackopenstack_stack_delete, Delete a Heat stack
Credential Setup
OpenStack tools take the clouds.yaml named by
the workspace's credentials_ref, a file on
the agent host at
credentials_dir/<workspace>/<credentials_ref>
holding exactly one cloud under clouds. That
cloud's auth block decides the project every call acts
in. An application credential is a good fit: create one
in the project and write its auth URL, ID and secret
into the cloud's auth block with
auth_type: v3applicationcredential. The
credential never leaves the agent host.
The client reads that file and no other
clouds.yaml or secure.yaml. A
file that is missing, empty, a symlink, readable by
group or other, or not holding exactly one cloud refuses
the call before the client runs. A workspace without
credentials_ref runs these tools on
whatever the agent's own account reaches; run one agent
per credential boundary, or bind each workspace. See
Workspace
credentials.
Examples
Once credentials are configured, the EEM agent can execute OpenStack tools on behalf of a workspace. See the EEM Overview for the full execution lifecycle.