You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: