Add aqs2001-2012 to the AQS Cassandra cluster.
- aqs2001
- aqs2002
- aqs2003
- aqs2004
- aqs2005
- aqs2006
- aqs2007
- aqs2008
- aqs2009
- aqs2010
- aqs2011
- aqs2012
See: T305568
Add aqs2001-2012 to the AQS Cassandra cluster.
See: T305568
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Configure AQS Cassandra hosts (codfw) | operations/puppet | production | +89 -2 | |
Dummy keys and certificates for cassandra (aqs) | labs/private | master | +984 -0 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Eevans | T307641 AQS multi-datacenter cluster expansion | |||
Resolved | Eevans | T307801 Bootstrap new Cassandra nodes (codfw) |
Change 802604 had a related patch set uploaded (by Eevans; author: Eevans):
[operations/puppet@production] WIP: Configure AQS Cassandra hosts
Change 802631 had a related patch set uploaded (by Eevans; author: Eevans):
[labs/private@master] Dummy keys and certificates for cassandra (aqs)
Change 802631 merged by MVernon:
[labs/private@master] Dummy keys and certificates for cassandra (aqs)
Change 802604 merged by MVernon:
[operations/puppet@production] Configure AQS Cassandra hosts (codfw)
These were installed with bullseye (the default), and we have thus far only run Cassandra on <= buster. We are missing the cassandradev component for bullseye, and jvm-tools and cassandra-tools-wmf are missing from bullseye main. In addition, cassandra-tools-wmf has a package dependency on python-yaml, which is no longer shipped in bullseye. I don't anticipate that we'd have any other issues running Cassandra on Debian 11.
An (unplanned) transition to bullseye feels a little like scope creep, but tackling this now means migrating 18 less nodes in the future (the 12 here, and the 6 additional going up in eqiad), which seems worth doing.
@hnowlan do you know if there would be any issues running RESTBase (AQS ~= RESTBase) on Bullseye?
From an exchange on Slack:
Eric Evans 9:50 AM @hnowlan do you know if we are running RESTBase on Bullseye anywhere? Do you know if there would be any problems running it on Bullseye? NodeJS version compatibility maybe?
Hugh Nowlan 9:56 AM Node is definitely the major blocker I can see - openjdk packages have already been ported to bullseye afaict
Eric Evans 9:56 AM oh, so that would be a blocker?
Hugh Nowlan 9:57 AM as far as I know buster’s version would be a fairly significant leap forward. Petr was working on this just before he left afaik but I dunno if he made any real progress
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2001.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2001.codfw.wmnet with OS buster completed:
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2002.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2002.codfw.wmnet with OS buster completed:
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2003.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2003.codfw.wmnet with OS buster completed:
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2004.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2005.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2006.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2004.codfw.wmnet with OS buster completed:
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2007.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2008.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2009.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2010.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2011.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage was started by mvernon@cumin2002 for host aqs2012.codfw.wmnet with OS buster
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2005.codfw.wmnet with OS buster completed:
It'll take the cookbooks a while to catch up (they back-off in increasing intervals waiting for puppet to be OK), but after some deployment-related hassle, all of these nodes have had puppet run to completion on them OK, so they should be good to go for you @Eevans .
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2006.codfw.wmnet with OS buster completed:
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2007.codfw.wmnet with OS buster completed:
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2008.codfw.wmnet with OS buster completed:
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2011.codfw.wmnet with OS buster completed:
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2009.codfw.wmnet with OS buster completed:
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2010.codfw.wmnet with OS buster completed:
Cookbook cookbooks.sre.hosts.reimage started by mvernon@cumin2002 for host aqs2012.codfw.wmnet with OS buster completed: