Good afternoon!
I just pulled the trigger on the maui migration of the following services:
* download.haiku-os.org
* buildbot.haiku-os.org (it will go away) -> build.haiku-os.org (new on maui)
In addition to nightly images, download.haiku-os.org also hosts "Haiku update
packages"
I've been pretty careful with naming + redirects to ensure existing haiku
installs should
still receive updates. I'm going to do some testing once the new dns entires
refresh.
download.haiku-os.org is one of the more complex + specialized systems we host
on baron.
I've done a lot of testing, but things could break. I'll fix them as soon as
issues pop up.
You might see "cdn.haiku-os.org" in the mix now (after redirects). This is an
s3 server
we're running to host build artifacts. A lot of our infrastructure has been
adjusted to
focus on storing artifacts in s3.
Changing to a common protocol such as s3 means everything is a lot more
flexible going
forward, and we rely less on spaghetti ssh / scp / rsync scripts and can handle
artifacts more
programmatically via python,rust,shell, etc
Keep me posted if anyone sees any huge issues. We do have a pretty simple
back-out plan.
-- Alex
