Wed, May 22
build: done & prod-worthy
siem: done & prod-worth
Our current thinking is that this is unlikely to help with SSL negotiation failures, and we'd rather stick with the stock version otherwise.
Tue, May 21
I linked this to T221008 because we're talking about making this change at the same time as we upgrade the queue servers and redis, since we'll need downtime and empty queues for both tasks.
Fri, May 17
Wed, May 15
We're planning for 2PM Thurs 5/16/2019.
Fri, May 10
Thu, May 9
civi1001 is done
Wed, May 8
This was fixed by T222761
Mon, May 6
@BBlack circling back on this, do you still see any issue now after the Silverpop SSL improvements?
Thu, May 2
Wed, May 1
Mon, Apr 29
this is done
this is deployed
This is done, now it's down to 74%.
Apr 18 2019
frav1002 is up and running
- aiderator is set up and seems to be working correctly
- dmarc parser is set up and seems to be working correctly
deployed and working
Apr 17 2019
Author: Jeff Green <email@example.com>
Date: Wed Apr 17 19:23:13 2019 +0000
Apr 16 2019
I think this is just par for the course when backing up directories where writes may be happening.
Versions available with Debian:
Note that we're using shiny server elsewhere at WMF and production puppet has modules/shiny_server already.
Upon first pass through the docs and software, the major difference as I see it is the authentication and user-access features--i.e. the emphasis on being able to run backend processes as different unix user based on i.e. PAM authentication. Also SSL support. It's not clear to me that we need to compartmentalize to different users. Also I think we may be able to put it behind a proxy for SSL and client authentication. We're going to set up a call to talk about technical options.
@Eileenmcnaughton is this correct?
I fixed this by puppetizing creation of /srv/org.wikimedia.civicrm-files/civicrm/templates_c.
It seems to be running fine now, if it crops up again we can reopen take another look.
Adjusted apt sources and pin settings short term, while we finish phasing out jessie hosts.
Done. payments1001 is configured as payments mariadb master for both sites.
Apr 15 2019
We've worked out all the identified upgrade-related issues with the test cluster, and are ready to upgrade the main cluster.
Americium is actually due for replacement in FY 2019-20, tentatively planned for first quarter. It would be a whole lot less disruptive to spin up the new host and switch to it than to do a Trusty to Stretch upgrade.
frdb1002 is done
frdb2001 is done
Apr 10 2019
mintaka is upgraded to stretch
Apr 9 2019
pay-lvs1001 and 1002 are done