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

single service on multiple machines issue #15

Closed
oshadmon opened this issue Apr 11, 2024 · 2 comments
Closed

single service on multiple machines issue #15

oshadmon opened this issue Apr 11, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@oshadmon
Copy link
Collaborator

brach os-dev

Steps:

  1. On Machine A start master node
make publish-service EDGELAKE_TYPE=master
make publish-deployment-policy EDGELAKE_TYPE=master
make agent-run EDGELAKE_TYPE=master
  1. On Machine B start operator node
make publish-service EDGELAKE_TYPE=operator
make publish-deployment-policy EDGELAKE_TYPE=operator
make agent-run EDGELAKE_TYPE=operator

Expect: Success
Actual: Master node drops when operator node gets deployed
Notes:

  • make sure to update LEDGER_CONN value in deployment.policy.XXX.json
  • we can have unique service d definition files, however ideally it'd be 1 file and have users updaate the deployment.node.json files
@oshadmon oshadmon added the bug Something isn't working label Apr 11, 2024
@joewxboy
Copy link
Member

joewxboy commented Mar 1, 2025

I believe query and operator nodes can co-exist now. Do we still need to get master and operator nodes co-existing as well?

@oshadmon
Copy link
Collaborator Author

oshadmon commented Mar 3, 2025

i believe Mark fixed this

@oshadmon oshadmon closed this as completed Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants