az
CLI and hadean
CLI by following the Prerequisites and Installing the SDK guides.hadean cluster -n <name> --cloud <provider> create
hadean cluster --name demo create -l uksouth
. For other locations, read about configuring Azure location.hadean cluster create --help
to see these options.hadean cluster --name demo create -l eu-west-2 --zone eu-west-2a --domain <domain>
.--name
| -n
--cloud-provider
| --cloud
| --provider
azure
/ aws
) to deploy the cluster to--location
| --region
| -l
--availability-zone
| --zone
--domain-name
| --domain
hadean cluster create
command will provision a new cluster in the location specified. You can check the status of your cluster(s) with the hadean cluster list
command.Ready
and this typically takes less than 5 minutes. You can watch
the list
command to avoid typing it in repeatedly.hello
demo - by using the hadean cluster deploy
command; pass the name of your cluster and the path to the application as arguments.--directory
argument to specify a directory containing other files to deploy along side your application.robot
that depends on the libraries ./lib/arms.so
and ./lib/legs.so
, then you could upload the files in your lib directory:./lib
will then end up in the working directory of your application.hadean cluster run
command; pass the name of your cluster and the path to the config file, see Configuring your application for details.--debug
argument to receive debug logs back from your application!--simple
to remove these.--detached
flag, the run
command will automatically start streaming application logs back from the cluster.standby_machines
set to greater than zero, you won't see this start up cost on every run. See Configuring your application for more information on how your configuration impacts scaling.--simple
and --no-parse-logs
to get out the raw log format. Then, you can use a tool like jq to process the JSON output and search for your module name.standby_machines
in your application config, the scheduler will down-scale your resources that are not in use. After this down scaling, exactly as many VMs as is specified in your config will remain.run
the time configured in machines_timeout
will be used to destroy all standby machines if no new application is run within that time. This allows you to iterate rapidly without leaving resources around.clean-up
command to fully remove all dynamic resources and start fresh.stop
command first, if something is running. You can always check using the status
command if you aren't sure. This command does not remove the scheduler itself, just all the resources that the scheduler has created.destroy
command:hadean-dynamic-{name}-{key}-resource-group
in all providers. Where name
is the first 6 characters of the cluster name, and key
is the first 6 characters of the cluster key. You can see this key by using hadean cluster list
before destroying.hadean-tf-{region}-{name}-{key}
with the same naming rules as the resource group in (1).hadean-tf
. The storage account name will be a hash. The storage container will have the name hadean-tf-{region}-{name}-{key}
.