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

Add multinode nomad support #52

Open
dlamarmorgan opened this issue Nov 2, 2022 · 2 comments
Open

Add multinode nomad support #52

dlamarmorgan opened this issue Nov 2, 2022 · 2 comments

Comments

@dlamarmorgan
Copy link
Collaborator

dlamarmorgan commented Nov 2, 2022

Currently, the Nomad HCL file generated by Storj-up will only work if the Nomad cluster has a single node with enough resources to run everything on the same node. This is due to the structure of the HCL file (only a single task group), as well as assumptions made in the config (localhost for several ENV variables.).

This should be updated to be more flexible and separate out unique services to their own task group. This will allow nomad cluster with multiple nodes to spread out the load.

Acceptance Criteria:

  • if you have a nomad cluster with multiple machines then generating a nomad HCL file should allow you to run the system like normal.
  • BONUS: anytime nomad cluster gets spun up which machine gets to run each server can change. make it so that you can specify which machine runs each server.
    • make it so that we can have some level of consistency with the service web GUI ip/ ports.
    • some potential solutions could be using service mesh, or reverse proxy, or consul
@iglesiasbrandon iglesiasbrandon moved this from Backlog to Up Next in Team Delivery Nov 9, 2022
@iglesiasbrandon iglesiasbrandon moved this from Up Next to Backlog in Team Delivery Nov 9, 2022
@stoweandi
Copy link

@dlamarmorgan is this something we still need to do?

@dlamarmorgan
Copy link
Collaborator Author

It would be a nice feature to have, but I'm not sure how much the nomad portion of storj-up is actually used. So it is probably very low priority.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants