I'd like to show you my playbooks, but unfortunately they're for a client - I can vouch for it being very easy to add nodes to a cluster etc. if you just have to edit an 'inventory' file and add IPs into the correct groups.
(NB: puppet and chef will automate your infrastructure too, it's just they're not as useful for things like rolling deployments in my experience because they're agent based, so it's harder to control when each server will update and restart services). A quick Google found: http://blog.michaelhamrah.com/2014/06/setting-up-a-multi-node-mesos-cluster-running-docker-haproxy-and-marathon-with-ansible/ which might be useful. The play books linked from that post are for bootstrapping a cluster, but it's pretty simple to add a second playbook to manage rolling deploys etc. There's some Ansible examples of rolling deploys (not Mesos specific) at : http://docs.ansible.com/guide_rolling_upgrade.html On 15 July 2014 14:41, Nayeem Syed <[email protected]> wrote: > thanks! > > do you have some examples of how you are using it with ansible? i dont have > specific preferences, whatever works really. > > > On Tue, Jul 15, 2014 at 2:35 PM, Dick Davies <[email protected]> wrote: >> >> You want a rolling restart i'd guess, unless you want downtime for some >> reason. >> >> We use Ansible, it's pretty nice. >> >> On 15 July 2014 10:47, Nayeem Syed <[email protected]> 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? > >
