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

Allow cluster definition to specify > 1 instances of a container #23

Closed
makeusabrew opened this issue Jan 8, 2014 · 2 comments
Closed
Labels

Comments

@makeusabrew
Copy link
Owner

Some clusters may well want several instances of a container running, particularly those which are replicas or workers etc. This should be specified on a per-cluster basis, and if used would cause containers to be suffixed ".1", ".2", ".3" etc.

@alexandrosm
Copy link
Contributor

Awesome. Had coded that into my half-baked pre-decking solution but didn't end up needing it yet so didn't bring it up, but it is something that would be nice to have in the future.

@makeusabrew
Copy link
Owner Author

This is in release 0.0.9, although has a few rough edges. At the moment it's in at cluster level (since that makes sense; a "prod" cluster might want a higher N of nodes than dev) but causes problems if a container binds fixed ports to the host, since they'll conflict with each other.

Closing for now but the next step would be to allow some sort of configuration templating where the "index" of a multi node can be inserted (e.g. for port offsets, logfile offets, whatever).

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

No branches or pull requests

2 participants