-
Notifications
You must be signed in to change notification settings - Fork 3
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
Upgrade servers to Ubuntu 20.04 #145
Comments
Ubuntu 20.04.01 (the point release that marks this as production ready) should be released on 06 Aug 2020. I imagine Bytemark will start supporting it from then. |
Noting some changes we'll likely have to make: |
BTW, there's still no option to start a server with Ubuntu 20.04 on Bytemark. We've been testing it out by creating a 18.04 server and upgrading it. |
I reached out to Bytemark support and they have no plans to add Ubuntu 20.04 to their list. We should be able to workaround this using their custom ISO option. |
@RobHooper Are there pros/cons to (incrementally) moving to a similar host that does offer Ubuntu 20.04? We use a Linode VPS for the CRM, and we have a Hetzner account for dedicated servers, which we can also use for their Cloud offering. I don't know how the hardware/performance and support compare. |
It's definitely worth looking at other providers and seeing how they compare. Its worth considering the flow of data between servers, especially when moving incrementally because bytemark to bytemark networking is will be very quick, the data stays in the same data centre probably moving at gigabit speeds. Bytemark to Linode (or anywhere else) will be slower, possibly only milliseconds slower but if you're sending a lot of data there is a bigger impact. |
All our Bytemark servers use less than 20GB, so not too much data. Besides Prometheus clients, the flows are:
standard-search currently builds an Elasticsearch index by crawling docs over the web, but this is inefficient, and I'm working on it building the index locally (during docs deployment), so that there won't be any data flow between them. |
Looking ahead, we're expecting a new data registry web service to read from kingfisher-replica, and to make requests to the services running on kingfisher-process (to initiate data collection and data processing). I haven't looked into whether Hetzner Cloud servers are in the same datacenters as dedicated servers, but if so this might be a reason to consider Hetzner Cloud. We don't have server specs for the registry, but right now I'm thinking it doesn't need a dedicated server. We're also expecting a flattening tool web service to read from kingfisher-replica. For the other services like Toucan, etc. which can be hosted anywhere, I still have a preference for fewer hosting providers, so ideally we would keep it to 3 like we have now (Hetzner, Bytemark, Linode). |
Noting that we might want to address #35 when moving to new servers. |
I'd agree this is worth looking into, and it is something Open Data Services may also be looking at for our own servers, since some of the reasons we chose Bytemark originally may no longer be true (particularly since they were aquired). |
If anyone does want to create an Ubuntu 20.04 server on Bytemark, you can do so by using the following custom ISO at the operating system step of server provisioning. You'll then need to open up the console and follow through the Ubuntu install steps. |
Regarding choice of host, I think the differences between the good providers are fairly minimal, and not important enough. I've seen good reviews for UpCloud and Vultr in terms of performance, but Dogsbody hasn't used them yet, so I prefer a host we know. DigitalOcean is also good, but we don't have an account with them. Dogsbody also mentioned Exoscale. All of these have official support on https://registry.terraform.io with respect to #156. Since we already have an account with Linode, I'm fine to continue with them. We use it for the CRM, and The Idea Bureau uses it for www.open-contracting.org. If we return to this question, I had started this spreadsheet in 2019. |
I've just raised a PR improving the Ubuntu 20.04 core build #281 |
Yes, let's go ahead with Linode. |
@RobHooper Per the email thread with Dan:
We only have two servers at Linode and haven't moved the others yet. If in your opinion Digital Ocean is a better choice, let's move the servers there instead. |
@jpmckinney We've had a discussion internally and we are happy continuing with Linode for now. Dan's message above was mainly a heads up in-case there were more issues but we are not at the point of recommending customers move away from Linode yet. That said, this could be a good prompt to test your stack on Digital Ocean making it easier to deploy there in the future. We could also investigate splitting hosting between the two ISPs. |
@RobHooper Sounds good, let's create an issue for that, but for now let's continue to upgrade Ubuntu and move to Linode. |
Closing in favor of #381, since we've been upgrading to 22.04. |
Once available on Bytemark.Document the process.Can consider moving someMove servers to Linode, if upgrading involves provisioning a new server.(Bytemark has very responsive support; I haven't had to interact with Linode recently.)Then, change the Ubuntu version in GitHub Actions workflows:
The text was updated successfully, but these errors were encountered: