lueschem/edi-cd

GitOps inspired fleet management for embedded devices.

edi-cd's Issues

Interlock playbook run with expected OS version

Current Situation

Imagine the following failure case:

1. An OS updated gets scheduled.
2. A configuration update gets scheduled.
3. The OS update fails and the device gets reverted to the previous installation.
4. The configuration update still gets executed but on the wrong OS setup.

Desired Behaviour

The configuration update shall fail if the preceding OS update failed.

Possible Solution

The expected OS version gets delivered to the gitops integration as a parameter and the gitops integration assures that the expected OS version matches the actual OS version.

Prevent accumulation of mender updates

Current Situation

If a device is offline then mender based updates will get scheduled but not executed. If the device is down for a longer period of time it might miss to receive multiple updates and therefore an accumulation of scheduled updates can occur.

Desired Situation

Planned updates for an offline device shall not lead to an accumulation of scheduled updates.

Possible Solution

Using this API call, previously scheduled updates shall be aborted:

1. prior to a new OS update or
2. prior to a configuration update in case there was no OS update required.