Choose where a machine runs
A machine is created on a hosting platform, in a region, in an availability zone. Name none of them and Machinery picks the first that has room.
The three fields
Section titled “The three fields”| Field | Flag | What it decides |
|---|---|---|
| Platform | --hosting-platform | who runs the clusters: deployport-compute, our own capacity, or uce, the clusters you own under our control plane |
| Region | --region | where inside that platform, by the slug a region listing answers |
| Zone | --availability-zone | where inside that region, by the slug a zone listing answers |
Leave --hosting-platform out and the machine is created on Deployport Compute. Leave --region out and the first region with room there is used. Leave --availability-zone out and the first zone with room in that region is used.
A zone belongs to a region, so --availability-zone is refused on its own.
List what a platform offers
Section titled “List what a platform offers”deployport machinery regions lsdeployport machinery regions zones us-east-2deployport machinery regions sizes us-east-2Each one takes --hosting-platform and answers about Deployport Compute without it. The first line of the answer names the platform that was asked.
regions lsprints one row per region, with the slug to pass to--region, and a DEFAULT column that marks the region a create which names none lands in.regions zonesprints one row per availability zone in that region.regions sizesprints the sizes that region can place: the literal to pass to--instance-type, its vCPU count, its memory and the CPU architecture.
A region or a zone with no cluster that can place a machine is left out, so nothing in these listings names a place a create would refuse.
The size
Section titled “The size”The size is a literal such as S, M, L or XL, as regions sizes spells it for the region. Leave --instance-type out and the machine is created at the smallest size that fits its kind. --architecture picks x86_64 or arm64.
A size the kind or the place cannot take is accepted at create and reported on the machine afterwards, naming the step that refused.
On Deployport Compute a worker takes its size from its worker pool rather than from --instance-type. Run machines in a worker pool covers that.
Create one in a named place
Section titled “Create one in a named place”In Machinery, open Machines and choose Add, or press A. New Machine lists the choices as rows: Kind, Worker pool, Place, Region, Zone, Size, Auto-stop and Name. Choose a row to change it, and the rows below it follow: the place decides the regions, and a region decides the sizes.
deployport machinery create --hosting-platform deployport-compute --region us-east-2 --availability-zone <zone> --instance-type M<zone> is one of the slugs regions zones us-east-2 printed.
Check it
Section titled “Check it”deployport machinery list --region us-east-2The machine is in the answer, and deployport machinery list --hosting-platform uce leaves it out when it runs on Deployport Compute. The place is on the machine’s own page in the console, under Region and Zone.
Next steps
Section titled “Next steps”- Launch your first machine creates one with every field left to the account’s defaults.
- Run machines in a worker pool shares one pool’s vCPU, memory and disk between several machines.
- Set what every machine inherits decides what a new machine gets when its launch names nothing.