Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Large merge-back of soak-cluster-deployers #27

Open
wants to merge 17 commits into
base: master
Choose a base branch
from

Conversation

MrMarvin
Copy link
Collaborator

Goal of this PR

Providing an idempotent, up-to-date and reliable set of well documented Ansible roles to automate the full life-cycle of Mesosphere DC/OS.

Things to consider

  • Dropping everything but the Ansible stack in this repository. Infrastructure definitions should be taken from the official Mesosphere DC/OS terraform stack.
  • Only well tested for DC/OS 1.12
  • Only supports CentOS 7
  • This PR is huge. I'd recommend to not go through each file, but rather inspect the state as-is in the source branch and decide from there if the architecture makes sense to be used for dcos-ansible.

Features

  • Fully automated DC/OS installation
  • Fully (or semi-, if desired) automated DC/OS upgrades
  • Automatic 'same version config updates' whenever the generated DC/OS config changes on bootstrap
  • Upgrade on same version, using the image_commit over version. Required for upgrading between non released versions.
  • Multiple roles, sharing code for DC/OS prerequisites in an additional role
  • Fully idempotent, single playbook
  • All variables securely name spaced (e.g. dcos['...'])
  • Not relying on inventory groups, using group_vars instead for usage in existing projects
  • Supports all current and future DC/OS config parameters via config.yaml pass-through.
  • Documentation and examples

@jrx jrx self-assigned this Oct 22, 2018
@MrMarvin
Copy link
Collaborator Author

MrMarvin commented Oct 22, 2018

As a preview on how this would end up in the Ansible Galaxy, I tweaked my personal Github fork to point to the feature branch per default (instead of master), added some Galaxy meta data files to the individual roles and created a new v0.42.2 git tag. The result is here: https://galaxy.ansible.com/mrmarvin/ansible_dcos
(Hopefully the transition pulling this to another Galaxy name space once this is merged is as easy...)

@jrx
Copy link
Collaborator

jrx commented Oct 29, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants