-
Notifications
You must be signed in to change notification settings - Fork 5
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
Nim-Waku Clusters #2
Comments
Questions:
|
@jakubgs hourly or daily works, but I think commits to master may be fewer so pushes could be better? The nodes of each network should find eachother but networks should not overlap. There are no specific hardware requirements |
What does "networks should not overlap" mean? |
Stable and Testing should not peer. |
Do we have some built-in way of preventing that? Or should it be done via firewall? |
I did some cleanup today and renamed old fleet to Also in the process I cleaned up a few smaller issues:
|
I deployed a 3 host
|
The
Seems to be related to native compilation and lack of some opcodes: |
Added a |
Okay, I built the image with @decanus am I using a wrong flag to disable native compilation flags? |
No idea, never seen this tbh. @zah maybe? |
@jakubgs, how have you tried to disable it? As far as I can tell, If you use the Dockerfile from this repo, you are supposed to either add that flag here: ... or pass it to the docker build with |
Yeah, and that's what I'm doing by adding
As well as when
https://ci.status.im/job/nim-waku/job/master/15/console So not sure what's missing. |
Ok wait, I think it did work. I re-created the container on
It seems like |
In order to re-arrange the layout to make use of the Terraform workspaces I had to do a bunch of changes to TF modules:
With this I was able to move
Now I can just do |
And added the |
Adjustment to |
Since waku-org/nwaku#310 was merged I've updated branches in https://ci.status.im/job/nim-waku/ jobs to I consider this done. If there's anything you want adjusted/changed please reopen this. |
Stable Cluster
This will be the first cluster, we will release to this cluster whenever a new tag is pushed indicating a stable release of WakuV2. This cluster should contain 3 nodes in geographically different regions so it is similar to the production clusters of what status is currently running.
Testing Cluster
This cluster will be trailing the master branch. It is the less stable testing cluster of WakuV2. The geographical location of this cluster is probably not as important as in the stable cluster, but there should also be multiple nodes.
The text was updated successfully, but these errors were encountered: