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

isolate instances #269

Open
vdloo opened this issue Oct 1, 2017 · 0 comments
Open

isolate instances #269

vdloo opened this issue Oct 1, 2017 · 0 comments

Comments

@vdloo
Copy link
Owner

vdloo commented Oct 1, 2017

currently it is not possible to run multiple instances of a raptiformica cluster on the same host(s), there are various places where state leaks. for example, all instances always bind consul on 8500 and this port is forwarded to the assimilating host here. Any isolated instance would retrieve data from the same distributed key value store. Additionally, the --cache-dir flag is not always respected. Furthermore, in various places (mainly the modules) repos are cloned directly from external sources instead of cached local copies, this enables out of band changes and that makes end to end testing with feature branches difficult.

ideally when all is completely isolated raptiformica can self-host a test environment, this would enable various useful features like verifying the mutable config is still valid and testing if any included modules break core functionality. it would also enable members of the cluster to act as ci machines instead of having to maintain machines outside of the cluster for that purpose in order not to pollute the 'live' environment

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

No branches or pull requests

1 participant