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

Automate multi-machine deployment #38

Closed
DieracDelta opened this issue Feb 22, 2022 · 2 comments
Closed

Automate multi-machine deployment #38

DieracDelta opened this issue Feb 22, 2022 · 2 comments
Assignees

Comments

@DieracDelta
Copy link
Contributor

Use Ansible to automate testing over multiple machines.

@DieracDelta DieracDelta self-assigned this Feb 23, 2022
@DieracDelta
Copy link
Contributor Author

DieracDelta commented Feb 25, 2022

This works but under the assumption we have this identity_mappings.json file. To get this to work with both with docker files (for fargate) and with ansible, we should have the example figure out its own public IP address (the easiest solution is with autonat), and parse the list of bootstrap nodes ip addresses from an inventory.yaml into a config.json that is provided to each node. We should:

  • remove the need for peer ids. This is really only helpful for debugging purposes.
  • move the bound port on into a cli variable or hardcode
  • move interface bound upon to cli variable
  • parse an inventory.yaml to find bootstrap nodes
  • add "expected" number of nodes to cli variable in the case of conductor node
  • specify node's role via cli variable (e.g. bootstrap, conductor, regular)
  • create a dockerfile that builds the statically linked executable with nix, then runs it

@nmccarty nmccarty transferred this issue from another repository Mar 7, 2022
@DieracDelta
Copy link
Contributor Author

closed by #35

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