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

launch a node in Singapore instead of HK (Asia) #83

Closed
Tracked by #1465
danisharora099 opened this issue Aug 22, 2023 · 4 comments
Closed
Tracked by #1465

launch a node in Singapore instead of HK (Asia) #83

danisharora099 opened this issue Aug 22, 2023 · 4 comments

Comments

@danisharora099
Copy link

in reference to waku-org/js-waku#1465 (comment), it seems a better option to launch a node in Singapore instead of Hong Kong for Asia

@jakubgs
Copy link
Member

jakubgs commented Aug 22, 2023

I don't think this is easily doable for 3 reasons:

  • We run Consul clusters in each Data Center we, as well as metrics and logs hosts.
    • I don't want to deploy a set of those only to support one or two nodes for this fleet.
  • We use a Terraform module called infra-tf-multi-provider that assumes a DC in Alibaba cloud.
    • The zone is hardcoded and changing that would not be trivial.
  • Migrating to Singapore would not really be doable for a lot of fleets because we could not preserve IPs.
    • Floating IPs are usually re-usable within a given DC, but not outside of it.

I don't think this change is worth the amount of effort it would require, unless you think it's very high priority.

And honestly, Waku protocol development would benefit from some bad latency =], that's what you should be building it for.

@fryorcraken
Copy link

Fair comment. Happy to close.

@jakubgs
Copy link
Member

jakubgs commented Aug 23, 2023

Now, if you do think this is actually important, we could do a Singapore node IN ADDITION to the Hong Kong one more easily.
Replacing Hong Kong one would be a massive pain, but if you just want one more host, for a total of 4 that would be feasible.

My question though would be, would that be specific to this fleet only? And if so, would it be for all stages or just one?

@danisharora099
Copy link
Author

All good for now, @jakubgs. Thanks for that.

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