Tuskar CLI commands draft

tuskar_commands.md

Tuskar CLI commands draft

Racks

tuskar rack-list

tuskar rack-show <name or id>

tuskar rack-create <name> \
    --subnet=192.168.1.0/255 \
    --capacities=total_cpu,64,CPU;total_memory,1024,MB \
    --slots=1 --resource-class=1

tuskar rack-update <name or id>
    # same possible args as for rack-create plus --name

tuskar rack-delete <name or id>

tuskar rack-add-node <rack name or id> <node id>

tuskar rack-remove-node <rack name or id> <node id>

Resource Classes

tuskar resource-class-list

tuskar resource-class-show <name or id>

tuskar resource-class-create <name> \
    --service-type=compute

tuskar resource-class-update <name or id>
    # same possible args as for resource-class-create plus --name

tuskar resource-class-delete <name or id>

tuskar resource-class-add-rack <resource-class name or id> \
                               <rack name or id>

tuskar resource-class-remove-rack <resource-class name or id> \
                                  <rack name or id>

Flavors

I'm not sure whether the command names should be like flavor-create or rather resource-class-create-flavor, given that we're effectively operating on a subresource under resource-class.

tuskar flavor-list <resource-class name or id>

tuskar flavor-show <resource-class name or id> <flavor name or id>

tuskar flavor-create <resource-class name or id> <new flavor name> \
    --capacities=cpu,10,count;memory,512,MiB;storage,10,GiB \
    --max-vms=10

(I know i'm inconsistent in units (CPU vs count, MB vs MiB), i took that from CURL samples, we'll need to decide which is correct and fix both places.)

tuskar flavor-update <resource-class name or id> <flavor name or id> \
    # same possible args as for resource-class-create plus --name

tuskar flavor-delete <resource-class name or id> <flavor name or id>

Data Center

tuskar provision-data-center

# tuskar provision-rack <rack name or id>