-
Notifications
You must be signed in to change notification settings - Fork 71
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
switch bootnode from aws to ovh #463
Conversation
@@ -4,7 +4,7 @@ | |||
"chainType": "Live", | |||
"bootNodes": [ | |||
"/ip4/54.89.28.91/tcp/30333/ws/p2p/12D3KooWKckYYKn2iztcKQcKjvdnBxs1yaL63WQigRtqMgNnmAK7", | |||
"/ip4/44.205.189.85/tcp/30333/ws/p2p/12D3KooWBWgvVtvKEvHDnhvtftUVFkBZhx23PHCqcXcoqGB5f6h7" | |||
"/ip4/15.204.212.186/tcp/30333/p2p/12D3KooWJSYJE71yzzw51TZb5tHb57HhbhQCxqeRRj9xU4QU1d7J" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so Staging currently has 1 bootnode on AWS and the other on OVH, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, I think for staging we can run entirely on OVH. Though? It's just us for staging, no high uptime is required. we risk if OVH down we're down entirely
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, let’s run staging with two OVH servers only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Defer to @imstar15 on whether we should update genesis config.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Switch bootnode on AWS to OVH nodes. Relevant infra changes are made separately.