Managing Machines

Machines join the platform by installing the agent. From there they are registered, tagged, and assigned to environments.

A machine is a Windows or Linux server (physical or virtual) running the Jaws Deploy Agent. The agent connects outbound to the control plane, registers itself, and waits for work. From then on, the machine is just another target.

Registration

Agent installation produces a registration command with a one-time token. Run it on the machine and the agent connects, identifies itself, and shows up in the workspace as a new unregistered target.

Finish the registration by assigning the target to one or more environments and adding tags. The platform won't deploy to it until an environment claims it.

// Tag conventions worth keeping

Pick these on day one, they're hard to change later

  • Role - role:app, role:db, role:cache, role:queue-worker.
  • Region - region:eu-west, region:us-east. Only if you have more than one region.
  • Capacity tier - size:large, size:small. Only if some steps need to run only on large machines.
  • Tenant - tenant:acme, tenant:globex. Only in multi-tenant setups.

Health

A target's health is the agent's connection status plus the outcome of its last deployment. The infrastructure view surfaces both. A disconnected agent shows up red; deployments to the target are blocked until it reconnects.