We use puppet with fabric to manage upgrades. We don't run puppet from cron, but we run on demand. Puppet manages the orchestration at host level. Fabric is used to connect/ssh to these host groups {masters, slaves, schedulers, zookeepers} and run puppet agent/apply. The masters and schedulers are running behind zookeeper. When we upgrade one master, the users won't be affected as the requests would go through other masters.
On similar note for slave upgrades, we enabled checkpoints. When the slave is restarted, the jobs running in it are not affected or restarted. On Tue, Jul 15, 2014 at 2:47 AM, Nayeem Syed <nay...@cronycle.com> wrote: > whats the best way to update mesos master instances. eg I want to update > things in there, install new frameworks, but at the moment I am ssh'ing to > the instances and installing them one by one. that feels wrong, shouldnt it > be done in parallel to all the instances? > > what do people currently do to keep all the masters in sync? -- Regards, Bhuvan Arumugam www.livecipher.com