[sle-beta] Transactional Updates in Leap 15

Thorsten Kukuk kukuk at suse.de
Thu Apr 5 07:32:50 MDT 2018

On Thu, Apr 05, Joe Doupnik wrote:

>     The offline duration part was addressed in my previous message (to
> Thorsten's). It is inherent with changes, and for sensitive situations an
> operational fallback is necessary to cover time and be a safety net.
>     Applying changes is still serial process, not parallel (else possible
> disaster and much buggy complexity, see any modern cooperative effort for
> examples). Atomicity/ACID is part of that design, at least as much as is
> reasonable.
>     As for efficiency and the like, the least complexity and detailed
> forward planning the better in the field, particularly if such configuration
> needs to be done when first installing a system.

Ok, now you perfectly described what transactional updates are doing :)


Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

More information about the sle-beta mailing list