Add swarm prod example - #2
Merged
Merged
Conversation
added 2 commits
June 19, 2017 17:30
LaurenSpiegel
approved these changes
Jun 20, 2017
Contributor
There was a problem hiding this comment.
can we use swarm secrets for these?
Author
There was a problem hiding this comment.
I forgot to mention it, thanks. I added it to the "further work" section because it will need another update to S3's docker-entrypoint.sh
Author
There was a problem hiding this comment.
Since what we store in redis is thrown away every 30s (or is it?), I think fits into the "resiliency" category since swarm scheduler will do its job of keeping one alive :)
rachedbenmustapha
force-pushed
the
ft/add-swarm-prod
branch
from
June 20, 2017 18:26
73b707b to
a8fba85
Compare
electrachong
approved these changes
Jun 21, 2017
This was referenced Jun 26, 2026
This file contains hidden or 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
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.
This docker service stack describes a simple Zenko production setup, including:
high availability and service resiliency (storage node excluded).
Needs scality/S3#777