status-im / infra-nimbus

Infrastructure for Nimbus cluster
https://nimbus.team
9 stars 5 forks source link

nimbus.prater: reduce layout to just 2 hosts #171

Closed jakubgs closed 8 months ago

jakubgs commented 8 months ago

This testnet will be dead within ~3 weeks.

jakubgs commented 8 months ago

Created a ticket to reinstall no longer used Prater hosts: https://client.innovahosting.net/viewticket.php?tid=999870&c=sfx4KSsm

We can use them for Jenkins and GitHub CI and other uses for now.

arnetheduck commented 8 months ago

is any of these removed nodes a bootnode? if yes, it needs to keep going.. https://github.com/eth-clients/goerli/blob/main/prater/bootstrap_nodes.txt

jakubgs commented 8 months ago

Whooooops, I forgot those were a thing. Those were the two AWS nodes:

stable-large-01.aws-eu-central-1a.nimbus.prater.statusim.net
testing-large-01.aws-eu-central-1a.nimbus.prater.statusim.net

Looks like I will have to re-create those.

jakubgs commented 8 months ago

Yeaaaaah, I think we can't recover the IPs for those bootstrap nodes. So we can't recover them. Sorry @arnetheduck .

arnetheduck commented 8 months ago

ok, how can we avoid that in the future? ie these nodes should ideally have some reasonably identifiable property somewhere - the same applies to mainnet etc, any transition needs to be managed

jakubgs commented 8 months ago

Well, best way to identify them is I guess to just use the word boot in the hostname, so it's clear which one is a bootstrap one.

Other than that maybe comments in layouts files and bootstrap section in README.

arnetheduck commented 8 months ago

+1 hostname