Re: [atomic-devel] Quorum-based voting for system upgrade

[Colin Walters <walters verbum org>]

On Wed, Sep 30, 2015, at 04:53 AM, Natale Vinto wrote:
> Hi,
> thanks for feedbacks. So, as far I understand, the logic (a module?)
> between daemonized rpm-ostree and any kubernetes node evacuation
> feature that move pods elsewhere, is responsible of upgrade and reboot
> machines, like having a lock grant by kubernetes successful evacuation
> operation.

Not sure I see why a lock would be needed; the PRs that sghosh linked for "draining"
should work well. 

> What about some underline IaaS platform exists, as for Openstack,
> would be Kubernetes to invoke for instance Compute API?

What would be the value of that over just invoking `systemctl reboot`?

That said, for guests in an IaaS environment, the OSTree (or in general
in-machine updates) can be replaced with building updated VM
images.  If one does that, then one would need to integrate with the
IaaS infrastructure for updates.