My first deploy

[paulmelnikow]

Hey maintainers,

I'd like to attempt a deploy on my own: see #1742 (comment) and #1742 (comment).

Would someone like to tag-team with me? The most helpful thing would be to monitor Sentry, though I know @espadrine hasn't been comfortable with anyone else having access to that. I think you could help in other ways, though, by hitting the server directly, monitoring the issues queue / twitter, and looking at the server status page.

This could be an evening this week, Oregon time, or Sunday afternoon, Chicago time. I've some availability next week too. Let me know if you're interested and let's see if we can find a time.

[paulmelnikow]

Just wanted to add: let's not cram to get stuff merged. If this deploy goes well let's plan on doing another one in a week.

[RedSparr0w]

I'd recommend during the weekend if possible, as we have pretty good uptimes.

I could modify my script at http://shields.redsparr0w.com/1568/ to send an email/notification during the time period if it detects any notable downtime?

[chris48s]

I should be available to keep an eye on things if you do Sunday afternoon central time. Evening pacific time doesn't co-ordinate well with my timezone.

Just in terms of what timezones maintainers are in (useful to know if we're trying to schedule stuff), based on the timestamp on everyone's last commit in the git log:

@chris48s +0100
@platan +0200
@PyvesB +0100
@RedSparr0w +1200

Might be easiest to co-ordinate on Discord for this one.

[paulmelnikow]

Mine's -0400 when I'm home, though I'm often working on the road, between -0500 and -0700. It's interesting to see everyone's time zones!

@RedSparr0w Maybe you could send the notifications to a new discord channel?

@chris48s Cool! Let's plan on Sunday.

[PyvesB]

Haven't yet planned my week-end, but I'll probably be able to keep an eye on things at times. 😉

[RedSparr0w]

Can have the notifications like this:
(note the last 12 hours were up & down a lot more than usual)

If the server has an uptime of <= 50% it will be marked as Unstable.
If the server has an uptime of >= 80% it will be marked as Stable.
Wait at least 10 minutes since the last notification before sending another one.
All the uptimes are based on request made within the last 5 minutes.

Possible changes to be made:

Setting	Old	New
Server Stable	>= 80%	>=90%
Server Unstable	<= 50%	<=40%
Min time between notifications	10 minutes	15 minutes
Group uptime by	5 minutes	5 minutes?

[espadrine]

I'm eager to tag along! I am in CEST (+0200).

I planned on doing an update (had a bit of computer trouble at home this month). I can do an update today if we fail to schedule something up.

[paulmelnikow]

Cool! Things are lined up for when @chris48 is gets online, which is a little over an hour from now, shortly after 10 a.m. UTC-5. Will be great for you to be around in case anything goes dreadfully wrong! At Chris's suggestion, let's coordinate on Discord.

[paulmelnikow]

s0 is live. We're going to monitor and if all looks good in a few hours we'll deploy to the other servers and the frontend.

[paulmelnikow]

And… it's live!

Thanks & congrats, everyone!

If anything systemic comes up, feel free to post here and one of the maintainers can reopen.