Ansible deploy script
If you're deploying Satellite to a cluster, you'll find that repeatedly changing its configuration on all of your Mesos hosts can involve some repetitive busy work. We've provided some Ansible Roles to help you automate these tasks.
These Roles deploy satellite-master and satellite-slave. systemd is used to launch and supervise the respective satellite processes. Execute either Role to deploy Satellite initially, OR to apply your latest configuration to an existing installation of Satellite.
Create or adjust the Ansible inventory for your Mesos cluster. You can just list hosts in a flat file (see inventory.sample), or build your inventory dynamically using the more sophisticated capabilities of Ansible. Either way, you should arrange your inventory such that it contains distinct groups, e.g. 'satellite_masters' and 'satellite_slaves', which contain the list of hosts to which you intend to deploy satellite_master and satellite_slave respectively.
Edit example_playbook.yml so that the settings are appropriate for your cluster.
Edit the Satellite configuration files specified by the variables in example_playbook.yml.
cd to the directory containing this file.
Run "ansible-playbook -i your_inventory example_playbook.yml" to deploy and start satellite_master on your Mesos master servers, and to deploy and start satellite_slave on your Mesos slave servers.
Want to use Supervisord (or another supervision solution) instead of Systemd?
If you don't want to use systemd, when running the satellite_master and satellite_slave Roles, make sure to exclude the tasks that have the tag "systemd", using "--skip-tags systemd".
This repository also includes some Ansible Roles which illustrate how you can supervise Satellite using Supervisord: satellite_master_supervisor and satellite_slave_supervisor. There's also a simple playbook that runs these roles.
These Supervisor Roles illustrate how you can deploy Satellite and make sure it stays running via Supervisor, but you probably won't be able to use the Roles on your cluster without modification. The Roles will actually install Supervisor on your hosts; assuming that you already have installed Supervisor, you'll want to skip the redundant Tasks. In your Playbook, you also will probably need to override some of the default variables exposed by Ansible's supervisorctl module (described here), so that you will be able to successfully communicate with your installation of Supervisor.