Skip to content

Add swarm prod example - #2

Merged
rachedbenmustapha merged 3 commits into
masterfrom
ft/add-swarm-prod
Jun 21, 2017
Merged

rachedbenmustapha merged 3 commits into
masterfrom
ft/add-swarm-prod

Conversation

@rachedbenmustapha

Copy link
Copy Markdown

This docker service stack describes a simple Zenko production setup, including:

  • Host filesystem-based, easy to back up volumes for data and metadata
  • Load balancer (nginx-based) on all nodes of the swarm
  • Multi-tiered networks (user-facing, DMZ and backend services)
  • Thanks to Docker Swarm and its overlay network, virtual ips and scheduler,
    high availability and service resiliency (storage node excluded).

Needs scality/S3#777

Comment thread swarm-production/README.md Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we use swarm secrets for these?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Comment thread swarm-production/README.md Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mention redis too?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 :)

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.

3 participants