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

Redeploy Demo network with NATs as the transport layer #3958

Closed
frrist opened this issue Apr 25, 2024 · 0 comments · Fixed by #4009
Closed

Redeploy Demo network with NATs as the transport layer #3958

frrist opened this issue Apr 25, 2024 · 0 comments · Fixed by #4009
Assignees
Labels
th/infrastructure Theme: Issues related to underlying infrastructure, such as servers and networking

Comments

@frrist
Copy link
Member

frrist commented Apr 25, 2024

Currently the production network is deployed using libp2p as the transport layer. It should instead be deployed using the default, NATS.
Additionally the default config used by bacalhau will need to be modified to include the production networks orchestrator IP address as the default orchestrator compute nodes use when they start up.

@frrist frrist added the th/infrastructure Theme: Issues related to underlying infrastructure, such as servers and networking label Apr 25, 2024
@frrist frrist changed the title Redeploy Demon network with NATs as the transport layer Redeploy Demo network with NATs as the transport layer Apr 25, 2024
wdbaruni added a commit that referenced this issue May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
th/infrastructure Theme: Issues related to underlying infrastructure, such as servers and networking
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants