Status: Accepted
Owner: ----
New issue 421 by [email protected]: Better ganeti upgrade experience (at
least on debian, to start)
http://code.google.com/p/ganeti/issues/detail?id=421
Currently to upgrade Ganeti you need to:
1) shut down ganeti on *all* nodes
2) upgrade the package on *all* nodes
3) backup the config
4) run cfgupgrade (& sometimes other commands) on the master
5) start ganeti & run gnt-cluster redist-conf
(see upgrade.rst).
This doesn't interact well with apt managed systems, which will upgrade a
new package "when it's available". Straw man solution (requires a design
doc):
1) gnt-cluster init & gnt-node add & gnt-cluster master-failover make sure
that nodes that are not the master don't upgrade ganeti (via a pin,
perhaps? or some other way?)
2) when the master upgrades its upgrade script also shuts down & upgrades
ganeti on all nodes in the cluster, and runs the full upgrade procedure as
above
3) everybody is happy, and just pushing a new version of ganeti to a repo
doesn't break all machines running that repo
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
