# Fleet configuration

Source: [https://docs.aventail.co.uk/docs/fleet/config-and-rollouts](https://docs.aventail.co.uk/docs/fleet/config-and-rollouts)

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

Current form and preview captured 2 October 2026; the later start/progress images are historical examples. Private details are obscured.

1.  **Choose settings and publish a revision**
    
    Select models, Serve settings, telemetry and log level. Add a change note and choose Publish revision. Review the new entry before applying it.
    
    This capture shows the existing v7 settings.
    
    [Screenshot: Configuration form and current revision — close-up from Fleet configuration and history.](https://docs.aventail.co.uk/img/guides/context/fleet-config.png)
    
2.  **Review every target before planning**
    
    Select Apply to fleet. The preview shows the target revision, excluded devices and actual ring membership. Planning alone dispatches nothing.
    
    A small fleet may have only one ring. Offline devices can be included; there is no per-device selector in this preview.
    
    [Screenshot: Configuration rollout preview showing one eligible device and three excluded because they already have v7.](https://docs.aventail.co.uk/img/control/fleet-2026-10-02/configuration-rollout-preview.png)
    
3.  **Start and check each ring**
    
    Start the first ring. Check applied revision, model state and a successful response before advancing.
    
    Historical interface example from the original documentation; current form and preview are shown in the previous steps.
    
    [Screenshot: Planned rollout panel with a control to start the rollout.](https://docs.aventail.co.uk/img/fleet-rollout-start.png)
    
4.  **Account for every device**
    
    Check errors and offline devices. Stop rollout prevents further promotion; do not assume it reverses applied changes.
    
    Historical interface example from the original documentation; current form and preview are shown in the previous steps.
    
    [Screenshot: Rollout progress panel showing ring progress and device outcomes.](https://docs.aventail.co.uk/img/fleet-rollout-progress.png)
    

Check the whole target fleet

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.

1.  Select the models to include. For each selected model, turn **Serve** on if devices should serve it.
2.  Set **Telemetry interval (seconds)** and **Log level**.
3.  Add a note explaining the change and select **Publish revision**.
4.  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

1.  In revision history, choose **Apply to fleet**.
2.  Inspect the preview of devices in each ring. Use the actual membership shown, especially for a small fleet.
3.  Select **Plan rollout** and check the plan. Planning alone does not dispatch changes.
4.  Start the first ring.
5.  Compare desired and applied revisions, inspect errors and test a model response.
6.  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.