Migration to new environment / Mastodon upgrade
Victor Matekole
Public
Seen by 542
We are preparing to migrate social.coop platform to a new set of servers and improved setup, consisting of the following:
— More capacity
— CDN/S3 integration using DreamObjects/Fastly
— Improved monitoring
— Upgrade Mastodon to 2.0
The service will be taken down around 02:00 CET (01:00 UTC) on Tuesday morning (24/10/2017) for approx 2hrs.
After service is restored there will be a few issues outstanding:
— Registration service will be down for a few days
— Additional configuration is needed to improve the current Status page
If there are any objections, please state them here. Thank you all.
Liaizon Wakest Mon 25 Jun 2018 9:38AM
so social.coop is now seriously behind in what version its running. what can we do to get upgraded to the newest version?
Victor Matekole Tue 26 Jun 2018 11:16AM
@wulee @mayel @matthewcropp .... Didn't want to create a new thread — In recent weeks, I think, we have all suffered from thread overload... Just wanted to note — whilst there are lots of discussions and proposals in formalising ops team to be concluded and ratified — I'd be happy to bump up Mastodon this week. From experience, users just want the latest version and are ok with some downtime as a result.
Robert Benjamin Tue 26 Jun 2018 6:43PM
Was really hoping we would have a coordinator in place ahead of the version upgrade. Were about 6 days out from that (2 days to close Tech Ops Team Formation Proposal and a 4 day nomination/poll vote after that). If the upgrade is really pressing or we're at risk of losing your contribution 2 weeks from now any chance that @wulee could shadow you on the process? Helpful or No?
Nick S Tue 26 Jun 2018 7:59PM
I probably could if it was at a time I wasn't otherwise engaged :). This could be tomorrow before 2pm GMT, for example, but I'm at work Thursday and Friday. Victor has my email address.
Victor Matekole Wed 27 Jun 2018 9:16AM
I offered to do this — one because I have a window of time this week only, as I am working on a migration, after then I have to switch my attention to a lagging project that puts me into another mode.
Second, it appears users feel secure that their instance is being kept up-to-date despite there being no notable advantage to their user experience. I am just trying to help and attend to users concerns.
I have previously offered "drive-by" terminal sessions on the documentation thread as I believe that is the best way for newcomers to learn — upgrading Mastodon (and generally Rails apps) can be an assault course sometimes, you can bet on something unexpected happening. But had no direct response to the offer ...
If you'd rather not do the upgrade and do it under the new team, I am also ok with that, just let me know... I will most likely do this late at night as that is my optimum time for doing such tasks.
Nick S Wed 27 Jun 2018 10:13AM
Personally I think you should do whatever's easiest for you, since there'll be other opportunities to do upgrades.
A possible compromise: is it possible to record your upgrade work so that people can watch over your shoulder at their convenience later? i.e. As if you had company, but executed at a time of your convenience.
Even just a written record of the steps and obstacles you encounter could be a useful guide for someone trying to to learn the job.
As an aside, I've been poking around on toot/trunk.social.coop. Various random questions occur to me as a result. What is the best way to ask, without annoying you with tons of them? (In the interim until we get GitLab working, which I hope will be where we do this eventually, yes?)
Robert Benjamin Wed 27 Jun 2018 7:58PM
I don't advocate for not doing if it this a good time. I do like @wulee suggestion that it be recorded. If that is possible. In either case I am not an authority on Mastodon upgrades so take that under consideration.
Not sure how kicking off upgrades were handled in the past but from a procedural point of view is it possible to float a URGENT (2 day) proposal to make the upgrade official (with you doing it) and to track hours as there is a remuneration pool ($250) that has been already been approved for this task?
Victor Matekole Thu 28 Jun 2018 11:36AM
As an aside, I've been poking around on toot/trunk.social.coop. Various random questions occur to me as a result. What is the best way to ask, without annoying you with tons of them? (In the interim until we get GitLab working, which I hope will be where we do this eventually, yes?)
I am not sure where the Gitlab topic is .... But out of security concerns — I suggest, just mail them to me and @mayel and we can post the thread at a later date when the Gitlab instance is ready.
Victor Matekole Thu 28 Jun 2018 11:44AM
In the past we tried to give 24hrs notice to users via Loomio/Mastodon ... Personally, I think a proposal is overkill, in the last wks I have had to cope wth a lot of information from Loomio, which has been disincentivising, I am probably not the only one ... Unless a Mastodon version holds a contentious feature like removing the ability to block other instances from connecting or publishing data automatically to a third-party... Upgrades should be done as a matter of course... IMHO
Paul Lindner · Fri 23 Feb 2018 6:57AM
Looks like you're on 2.1.3 now. Congrats!