Felix Kronlage-Dammers
1142e50270
|
||
|---|---|---|
| config | ||
| vendor | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| go.mod | ||
| go.sum | ||
| main.go | ||
| servers.go | ||
| servers_list.go | ||
| servers_status.go | ||
| snapshots.go | ||
| snapshots_age.go | ||
| snapshots_count.go | ||
| storages.go | ||
| storages_list.go | ||
README.md
gridscale-check
A variety of commands to check various aspects of your IaaS-assetts at gridscale. This check makes use of gsclient-go.
The check-command looks in config/check.toml for a config file containing (for now) just the
gridscale user and token. These can also be set via the environment:
GRIDSCALE_USER='userid'
GRIDSCALE_TOKEN='token'
commands
snapshots
$ gridscale-check snapshots count -w 2 -c 1 -u <uuid-of-storage>
$ gridscale-check snapshots age -w 1 -c 2 -u <uuid-of-storage>
servers
state of the server
$ gridscale-check servers state -t server.status -s active -u <uuid-of-server>
check number of cpu cores or memory assigned
n - Max Amount m - Min Amount
$ gridscale-check servers state -t server.cores -u <uuid-of-server> -n 6 -m 4
$ gridscale-check servers state -t server.memory -u <uuid-of-server> -n 6 -m 4
check IP that is assigned
Either with a value to compare (-c) or by matching the relation (-r):
$ gridscale-check servers state -t ip.assigned -u <uuid-of-server> -c 192.168.10.20
$ gridscale-check servers state -t ip.assigned -u <uuid-of-server> -r <uuid-of-ip-object>
check wether a certain firewall template is enabled
$ gridscale-check servers state -t firewall.template -u <uuid-of-server> -r <uuid-of-ip-object>
helper commands
There are some helper commands, such as listing servers and storages:
$ gridscale-check servers list
$ gridscale-check storages list