RESALLOC-I...-POWERVS-VM(1)
β¨ RESALLOC-I...-POWERVS-VM(1) β¨
okay so bestie, welcome to the manual page for resalloc-ibm-cloud-powervs-vm β it's a generated Python manual, it lives in the resalloc-ibm-cloud family, and it's your little helper for spinning PowerVS instances up and down in IBM Cloud. let's get into it π
π NAME π
resalloc-ibm-cloud-powervs-vm
that's it. that's the name. iconic. π
π¦ SYNOPSIS π¦
resalloc-ibm-cloud-powervs-vm [-h] --token-file TOKEN_FILE [--log-level
LOG_LEVEL] --crn CRN {create,delete} ...
so basically you pick a subcommand β either create or delete β and you feed it a token file and a CRN, and you're off π
πΈ POSITIONAL ARGUMENTS πΈ
resalloc-ibm-cloud-powervs-vm createβ makes you a brand new PowerVS instance in IBM Cloud. main character energy fr β¨resalloc-ibm-cloud-powervs-vm deleteβ yeets a PowerVS instance out of IBM Cloud, by its name. bye bestie π
π
COMMAND resalloc-ibm-cloud-powervs-vm create π
here's how you call it:
usage: resalloc-ibm-cloud-powervs-vm create [-h] --playbook PLAYBOOK
--image-uuid IMAGE_UUID
--ssh-key-name SSH_KEY_NAME
--processors PROCESSORS
[--processor-type
{dedicated,shared,capped}]
--ram RAM
[--network-id NETWORK_ID
[NETWORK_ID ...]]
[--storage-type
{tier1,tier3}]
[--volumes VOLUMES [VOLUMES
...]]
[--tags TAGS [TAGS ...]]
[--system-type {s922,e980}]
[--no-rmc]
[--storage-pool
STORAGE_POOL]
name
and then there's the positional:
nameβ the name. no description in the original, she just needs a name π«Ά
β OPTIONS resalloc-ibm-cloud-powervs-vm create β
okay this is the big one, buckle up π
--playbook PLAYBOOKβ path to the playbook π--image-uuid IMAGE_UUIDβ the UUID of the image you wanna use πΌοΈ--ssh-key-name SSH_KEY_NAMEβ name of the SSH key to use for the instance π--processors PROCESSORSβ how many processors (that's CPU cores, bestie) πͺ--processor-type {dedicated,shared,capped}β processor type. your options are literallydedicated,shared, orcappedβ pick your vibe β‘--ram RAMβ RAM memory, measured in GB π§--network-id NETWORK_ID [NETWORK_ID ...]β the ID of the network to attach to the instance. yes you can pass more than one, she's flexible π--storage-type {tier1,tier3}β storage tier type.tier1is SSD,tier3is HDD πΎ--volumes VOLUMES [VOLUMES ...]β extra volumes to attach, and they gotta be in the format'name:size_gb:type'π¦--tags TAGS [TAGS ...]β a space separated list ofkey:valuetags, likeapp:coprπ·οΈ--system-type {s922,e980}β machine type.s922ore980, those are the choices π₯οΈ--no-rmcβ do not wait for Resource Monitoring and Control to be ready. skipping the wait, living on the edge π--storage-pool STORAGE_POOLβ the storage pool to create the volumes and VMs in. if you don't specify it, the default gets used π«§
π COMMAND resalloc-ibm-cloud-powervs-vm delete π
usage: resalloc-ibm-cloud-powervs-vm delete [-h] name
and the positional:
nameβ the name again. that's how she finds it π
π OPTIONS π
these are the top-level ones, they apply to the whole thing:
--token-file TOKEN_FILEβ path to the IBM cloud token file π--log-level LOG_LEVELβ ngl bestie, the original manual page gives zero description here. it's giving mystery. it's just--log-level LOG_LEVELand nothing else π--crn CRNβ the CRN of the PowerVS instance, and it's used to get credentials πͺͺ
π AUTHOR π
Copr team <copr-team@redhat.com> β ty for your service, legends π«Ά
real talk: this page is fromresalloc-ibm-cloudversion1.0, dated2025-10-03. that's the whole tea. go make some instances, bestie, you got this π β¨π
π¦ where this page comes from
- fedora 43: resalloc-ibm-cloud 3.4-1.fc43 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms