trs/wip/deploy #11
Draft
trs/wip/deploy #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To do this, I think we need to bring in a lot more of the deployment
process (which is our longer-term goal anyway).
I'm 50% sure the organization of tasks into tasks/source.yaml isn't the
right factoring for deploys. I'm 90% sure that the bits in
tasks/uwsgi.yaml, tasks/python.yaml, and other files are a good
factoring, though.
Todos:
- Merge in backoffice.git into this repo, with contents under a subdir
(for now), while preserving git history. This will let files in there be
managed/installed by Ansible instead of by running git pull on
backoffice.
- Port and adapt documented deploy steps into idempotent tasks in one
or more Ansible playbooks.
- Bring Apache and Shibboleth management under the wings of Ansible
too. I would expect to merge in backoffice-apache2.git and
backoffice-shibboleth.git into this repo too, along similar lines to
(1).
There's a continuum here though, and each item above can be split into
separate, iterative steps that rachet towards the goal. That said,
upfront time aside, it might be easier to do things in one fell swoop to
reduce the overhead of coordinating changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automate deployments
To do this, I think we need to bring in a lot more of the deployment
process (which is our longer-term goal anyway).
I'm 50% sure the organization of tasks into tasks/source.yaml isn't the
right factoring for deploys. I'm 90% sure that the bits in
tasks/uwsgi.yaml, tasks/python.yaml, and other files are a good
factoring, though.
Todos:
Merge in backoffice.git into this repo, with contents under a subdir
(for now), while preserving git history. This will let files in there be
managed/installed by Ansible instead of by running git pull on
backoffice.
Port and adapt documented deploy steps into idempotent tasks in one
or more Ansible playbooks.
Bring Apache and Shibboleth management under the wings of Ansible
too. I would expect to merge in backoffice-apache2.git and
backoffice-shibboleth.git into this repo too, along similar lines to
(1).
There's a continuum here though, and each item above can be split into
separate, iterative steps that rachet towards the goal. That said,
upfront time aside, it might be easier to do things in one fell swoop to
reduce the overhead of coordinating changes.
The WIP here adds management of uWSGI apps, but it alone is not
sufficient for managing deploys.