resalloc-ibm-cloud-vm - Man Page

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

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

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]
                                   [--no-floating-ip]
                                   --subnets-ids SUBNETS_IDS [SUBNETS_IDS ...]
                                   [--additional-volume-size ADDITIONAL_VOLUME_SIZE]
                                   name

name

--playbook PLAYBOOK

Path to 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

e.g. cz2-2x4

--floating-ip-name FLOATING_IP_NAME

--no-floating-ip

Don't use floating IPs (for VPN)

--subnets-ids SUBNETS_IDS [SUBNETS_IDS ...]

Space separated list of subnets ids. In case zones are different than a basic zone, then specify subnet id with zone colon separated like this: zone-1:subnet-id-1 zone-2:subnet-id-2

--additional-volume-size ADDITIONAL_VOLUME_SIZE

Allocate additional volume of given size in GB

usage: resalloc-ibm-cloud-vm delete [-h] name

name

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

--token-file TOKEN_FILE

Path to IBM cloud token file

--zone ZONE

default IBM Cloud zone. e.g. jp-tok, us-east, us-west, ...

--log-level LOG_LEVEL

Copr team <copr-team@redhat.com>