Fleet configuration
Choose the fleet's models and settings, publish a revision, then apply it to existing devices through a rollout.
Publish and apply a fleet configuration
Slide 1 of 6: Fleet configuration and history.
The rollout preview determines the target devices; it does not offer a per-device selector. A small fleet may fit into one ring, including offline devices. Review the scope before starting it.
Read the configuration and rollout steps
Publish a revision
Open Fleet operations → Enrollment & config and find Fleet configuration. Publishing requires Fleet Admin or Super Admin. Record the current settings before changing them.
If the list is empty, first add a model to the organisation. A user with model-management permission can use Move to [organisation] on an owned, unshared personal model. This move is permanent: storage moves to the organisation, the model leaves the personal library, and personal devices can no longer download it. Review the confirmation before moving a model.
If a read-only trial banner is shown, restore the organisation’s access before publishing or applying changes.
- Select the models to include. For each selected model, turn Serve on if devices should serve it.
- Set Telemetry interval (seconds) and Log level.
- Add a note explaining the change and select Publish revision.
- Check the new version and settings under Revision history.
New enrollments use the latest revision immediately. Existing devices receive the revision when you apply it through a rollout. Treat each revision as a snapshot; publish another revision to change its settings.
A Serve setting requests serving state. Confirm the model is installed and an inference request succeeds before treating that device as ready.
Apply in rings
- In revision history, choose Apply to fleet.
- Inspect the preview of devices in each ring. Use the actual membership shown, especially for a small fleet.
- Select Plan rollout and check the plan. Planning alone does not dispatch changes.
- Start the first ring.
- Compare desired and applied revisions, inspect errors and test a model response.
- Advance the next ring only when the previous ring meets your acceptance checks.
Ring promotion is manual. Fleet Manager, Fleet Admin and Super Admin can operate rollouts. Coordinate with other administrators before promoting a change.
Stop or recover
Read the scope shown by Stop rollout before using it. Stopping promotion must not be treated as undoing configuration already sent to devices.
If a started ring has a problem, stop further promotion, record affected devices and check their actual state. To restore previous settings, prepare a new revision and review its rollout. Do not rely on an automatic rollback.
Check offline devices
Keep offline devices in the review list. After reconnection, inspect the desired/applied revision and model status, then repeat the acceptance test. Close the rollout only when every intended device is accounted for or an exception is documented.