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

Implementation of Multi-Planet Robot Nodes #121

Open
linqingping opened this issue Aug 9, 2023 · 3 comments
Open

Implementation of Multi-Planet Robot Nodes #121

linqingping opened this issue Aug 9, 2023 · 3 comments

Comments

@linqingping
Copy link

How to implement network controller deployment composed of multiple planetary nodes

@zikuan-wang
Copy link

same issue

@ifyz
Copy link

ifyz commented Jan 4, 2025

same issue

I’ve been thinking about it, and if a single ztncui is managing multiple ZeroTier clients as planets, it’s still fundamentally centralized. If the server hosting the ztncui controller goes down, it would still disrupt normal usage.

A better solution might be to deploy multiple ztncui instances using the same network ID, with the controllers keeping their data in sync. But that approach might be tricky to implement.

@ifyz
Copy link

ifyz commented Jan 4, 2025

Here is a possible solution, though it has not been tested:

  1. Deploy ztncui and the ZeroTier server in Docker containers on multiple servers, ensuring that all ztncui instances share the same network ID.

  2. Centralize all ZeroTier servers to create a planet configuration.

  3. Replace the planet file on each ZeroTier server with the configuration created in step 2.

  4. When adding any network configuration, it must be seted on all ztncui panels
    (or you can write a script to manage and synchronize all ztncui configs).

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

3 participants