Skip to Content

Updates

Updates on the host and from Rookery, hosts that are behind, and what Rookery leaves out.

What updates itself

Ubuntu security updates and Firefox's vendor updates install automatically. The host never reboots on its own. Status says when a reboot is needed.

What you update

HowUpdates
Update on the overview, or rookery run HOST updateapt update and dist-upgrade, then what plugins installed, such as the Unity CLI, to their latest versions
Reboot, or rookery run HOST rebootRestarts the host to finish updates
Apply this configurationRuns the role again, which brings new or changed features and settings, rookeryd and box, and plugin actions and services
rookery plugin updateYour plugins, to the latest version of their registry (Updating a plugin)

The versions a plugin installs are the least ones, so applying the configuration again does not go back to them after an update.

Rookery itself

rookery update --check     # is there a newer release?
rookery update             # download it, check its SHA-256 and replace this program

rookery update takes the same archive as the install script. It offers only full releases, not pre-releases such as 0.4.0-rc.1, and moves from a pre-release to its release. A container is updated by pulling a newer image. rookeryd and box travel inside rookery. A host gets the new ones when you apply its configuration. Its overview says when its tools are of another version than your Rookery.

A host whose rookeryd is older than Rookery needs is marked old controller in rookery ls. Its sessions, files and rookery exec work, but its actions and port forwarding need a newer rookeryd. The host's page and its actions say what updates it, rookery apply HOST or, for a managed host, rookery run HOST install-controller. A Rookery that meets a newer rookeryd is out of date: update it. It refuses the profile a newer Rookery left on the host rather than misread it. rookery update --from URL takes the releases from a mirror instead, and the setting releases keeps one.

A client refuses a server with an older API, and says to update the server first. Update a server, then its clients, then its hosts.

Hosts that are behind

Applying records on the host which Rookery and which plugins the configuration came from, with each plugin's version and a digest of its files. Rookery compares that with what it would apply now. When a plugin was updated, or Rookery was, the overview says what changed, such as unity 1.0.0 → 1.1.0. A plugin that changed without a new version shows as (changed). A Rookery server's host list marks such a host behind, and hosts.get says what changed.

A host that was applied before this record existed says nothing yet. Applying it once records it.

Bringing hosts up to date

rookery rollout                     # every host that is behind
rookery rollout --update --reboot   # and run Update, and reboot where needed
rookery plugin update && rookery rollout   # update the plugins, then the same

The hosts are taken one at a time, by name. Each is applied and then checked. Its rookeryd has to answer with this Rookery's version and the host must no longer be behind. Its Status action has to end well too. Hosts that are current are skipped. The first host that fails stops the roll-out, and the hosts after it are not touched.

OptionDoes
--updateRuns the host's Update action after applying. If it ends badly, that host is finished and the roll-out stops after it
--rebootReboots a host that says it needs it, waits up to ten minutes for it to answer again, then checks it. A host with running sessions is not rebooted, and the roll-out stops there
--forceReboots also while sessions run, which ends them
--allApplies the hosts that are current too

With a Rookery server set, the roll-out is a job of the server. On the Plugins tab, after an update, r lists the hosts with what changed and starts on a second r. R does the same with --reboot.

What applying again keeps

Applying again keeps the agent's home and workspaces, sign-ins, the secrets that were sent, running sessions, and the channel's messages. A tool installed at a newer version than the profile names stays at that version. A plugin service restarts only when its script or unit changed, and the output says which.

A task, service or channel topic a plugin no longer has is gone after applying. What a plugin's own Ansible tasks installed stays on the host.

After changing versions

Applying does not restart desktops that are already running or turns an agent is in the middle of. After changing versions, a service's environment or unit files, restart the agent's user services in a quiet moment, or reboot.

Applying restarts rookeryd only when its program or unit changed, because a restart ends the sessions it holds. New actions, services and channel topics only need a reload, which applying does.

What Rookery does not do

  • The bootstrap retries an install that did not finish, but it does not pull Git branches or replace a release that completed. A host changes when you apply the role again.
  • No automatic firmware updates, encrypted unattended boot, swap tuning, offline package bundles, or transactional updates with rollback.
  • Laptop power settings are defaults for fresh physical installs. Settings the user changed in XFCE win. Reboot after the first laptop setup.

Data

Application data is stored under /home/agent and /srv/agent. Back both up before upgrades, with the Backup plugin or your own tools.

Edit on GitHub

Last updated on

On this page