|Open||None||T53494 Use Beta cluster as a true canary for code deployments (epic)|
|Open||None||T87220 Minimize differences between beta and production (Tracking)|
|Resolved||• AlexMonk-WMF||T38891 Setup poolcounter daemon in Beta Cluster|
|Declined||None||T38892 [OPS] puppetize poolcounter|
|Resolved||Joe||T112501 Create a poolcounter instance in deployment-prep|
|Resolved||Andrew||T112200 Update remaining virt nodes to kilo|
(In reply to Antoine "hashar" Musso from comment #2)
Following a discussion with Tim Starling during the hackathon, poolcounter
is not really needed on beta.
Eh, I thought the purpose of the beta cluster was to mirror production. Can you please elaborate on why PoolCounter isn't needed on beta?
Per discussion with Tim earlier we do not need a PoolCounter on beta. There is simply not enough traffic / contention there to have any use for the Poolcounter nor to find out whether it is working properly.
According to T112501 , deployment-poolcounter01.deployment-prep.eqiad.wmflabs is the Poolcounter instance since September 2015.
wmf-config/LabsServices.php:$wmfAllServices['eqiad']['poolcounter'] = [ wmf-config/LabsServices.php: '10.68.19.181', # deployment-poolcounter01.deployment-prep.eqiad.wmflabs