You are browsing a read-only backup copy of Wikitech. The primary site can be found at

Depooling servers

From Wikitech-static
Revision as of 07:00, 29 September 2015 by imported>Muehlenhoff (Add documentation for mw* et al)
Jump to navigation Jump to search

Contains various ways to depool different servers. In a glorious future, we'd just need to do conftool depool <service> <node> but we aren't there yet!

cp*** machines

These are the varnish frontends, and should be depooled via conftool. To fully depool a server, do as root on palladium:

confctl --tags dc=eqiad,cluster=<cluster-name>,service=varnish-be --action set/pooled=no <server-fqdn>
confctl --tags dc=eqiad,cluster=<cluster-name>,service=varnish-be-rand --action set/pooled=no <server-fqdn>
confctl --tags dc=eqiad,cluster=<cluster-name>,service=varnish-fe --action set/pooled=no <server-fqdn>
confctl --tags dc=eqiad,cluster=<cluster-name>,service=nginx --action set/pooled=no <server-fqdn>

You can find out <cluster-name> from looking at conftool-data/nodes/ in the operations/puppet repository.

mw* machines (and others)

The mw* application servers and other servers managed via pybal are depooled by editing a configuration file in the /srv/pybal-config directory on palladium. This is documented at