RESALLOC-IBM-CLOUD-VM(1)

πŸ“¦
version 3.4 Β· 3 versions
, in fedora 43

πŸ’– resalloc-ibm-cloud-vm πŸ’–

okay bestie, so this is resalloc-ibm-cloud-vm, and it lives in the Generated Python Manual collection. It's your little cloud-VM wrangler for IBM Cloud β€” spins 'em up, tears 'em down, and sweeps up the leftover IPs. no cap, she's a whole vibe. πŸ¦‹


✨ NAME ✨

resalloc-ibm-cloud-vm β€” she makes and unmakes IBM Cloud instances, that's the whole personality πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

resalloc-ibm-cloud-vm [-h] --token-file TOKEN_FILE [--log-level
LOG_LEVEL] [--zone REGION] [--region REGION] {create,delete,delete-free-
floating-ips} ...

🌸 POSITIONAL ARGUMENTS 🌸

like, you gotta pick a subcommand. it's giving "choose your own adventure" ✨

  • resalloc-ibm-cloud-vm create β€” Create an instance in IBM Cloud πŸ‘‘
  • resalloc-ibm-cloud-vm delete β€” Delete instance by it's name from IBM Cloud πŸ—‘οΈ
  • resalloc-ibm-cloud-vm delete-free-floating-ips β€” Clean all IPs without an assigned VM 🧹

🫢 COMMAND 'resalloc-ibm-cloud-vm create' 🫢

usage time, and yes it's a long one, she's high maintenance but worth it:

usage: resalloc-ibm-cloud-vm create [-h] --playbook PLAYBOOK
                                    --image-uuid IMAGE_UUID --vpc-id
VPC_ID
                                    --security-group-id
SECURITY_GROUP_ID
                                    --ssh-key-id SSH_KEY_ID
                                    --instance-type INSTANCE_TYPE
                                    [--floating-ip-name FLOATING_IP_NAME
|
                                    --floating-ip-uuid FLOATING_IP_UUID
|
                                    --no-floating-ip |
                                    --floating-ip-uuid-in-subnet
SUBNET-ID FLOATING-IP-UUID]
                                    --subnets-ids SUBNETS_IDS
[SUBNETS_IDS ...]
                                    [--additional-volume-size
ADDITIONAL_VOLUME_SIZE]
                                    [--resource-group-id
RESOURCE_GROUP_ID]
                                    [--tags TAGS [TAGS ...]]
                                    name
  • name β€” yep, that's the positional one, the instance name, the moment πŸ’…

✨ OPTIONS 'resalloc-ibm-cloud-vm create' ✨

  • --playbook PLAYBOOK β€” Path to playbook πŸ“– (she needs to know where the playbook lives)
  • --image-uuid IMAGE_UUID β€” UUID of the image to use πŸ–ΌοΈ
  • --vpc-id VPC_ID β€” the VPC id, that's it, that's the whole description 🫧
  • --security-group-id SECURITY_GROUP_ID β€” the security group id, also vibes only ✨
  • --ssh-key-id SSH_KEY_ID β€” ssh key id, so you can actually get in πŸ”‘
  • --instance-type INSTANCE_TYPE β€” e.g. cz2-2x4 πŸ‘‘
  • --floating-ip-name FLOATING_IP_NAME β€” floating IP by name, if that's the route you're taking 🎈
  • --floating-ip-uuid FLOATING_IP_UUID β€” floating IP by UUID instead, pick your fighter 🎈
  • --no-floating-ip β€” Don't use floating IPs (for VPN) πŸ™ˆ
  • --floating-ip-uuid-in-subnet SUBNET-ID FLOATING-IP-UUID β€” Add a Floating IP UUID into the list of IPs that can be used for the corresponding subnet ID. Depending on the $RESALLOC_ID_IN_POOL (given by Resalloc server) the script assigns the newly started machine n-th IP from the list. 🧠✨
  • --subnets-ids SUBNETS_IDS [SUBNETS_IDS ...] β€” Space separated list of ZONE:SUBNET_ID pairs. The ZONE must be a valid ZONE ID within the specified --region (e.g., 'eu-es-2' within 'eu-es' region). 🌍
  • --additional-volume-size ADDITIONAL_VOLUME_SIZE β€” Allocate additional volume of given size in GB πŸ’Ύ
  • --resource-group-id RESOURCE_GROUP_ID β€” Resource group id, get it from $ ibmcloud resources πŸ”
  • --tags TAGS [TAGS ...] β€” Space separated list of key:value tags, e.g. app:copr 🏷️

πŸ’œ COMMAND 'resalloc-ibm-cloud-vm delete' πŸ’œ

short and iconic, honestly:

usage: resalloc-ibm-cloud-vm delete [-h] name
  • name β€” the instance name to yeet πŸ—‘οΈ

🌈 COMMAND 'resalloc-ibm-cloud-vm delete-free-floating-ips' 🌈

the cleanup queen, no arguments, no notes:

usage: resalloc-ibm-cloud-vm delete-free-floating-ips [-h]

⭐ OPTIONS ⭐

these ones are top-level, they apply to the whole resalloc-ibm-cloud-vm situation πŸ’–

  • --token-file TOKEN_FILE β€” Path to IBM cloud token file πŸ”
  • --log-level LOG_LEVEL β€” log level, that's the description, she keeps it mysterious πŸ™ˆ
  • --zone REGION β€” default IBM Cloud zone. e.g. jp-tok, us-east, us-west, ... 🌎
  • --region REGION β€” default IBM Cloud zone. e.g. jp-tok, us-east, us-west, ... 🌍
bestie don't panic β€” --zone and --region genuinely do have the same description in the original. not a typo on my part, I promise 🫢

πŸ‘‘ AUTHOR πŸ‘‘

Copr team <copr-team@redhat.com> πŸ’Œ


and that's the whole page!! mwah πŸ’…

this was resalloc-ibm-cloud 1.0, dated 2025-10-03 β€” so like, she's resalloc-ibm-cloud version 1.0, born 2025-10-03, and she ate. periodt. πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from