View source for Depooling servers

Contains various ways to depool different servers. In a glorious future, we'd just need to do <code>conftool depool <service> <node></code> 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 any puppetmaster frontend:

<code>
$ confctl select dc=<dc>,cluster=<cluster-name>,name=cp*** set/pooled=no
</code>

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

An easier option is to ssh into the server and just run
<code>
$ sudo -i depool
</code>

Note the use of sudo -i. depool needs environment variables to get access to etcd.

== mw* machines (and others) ==

The mw* application servers and various other servers are managed by [[PyBal]] directly in Etcd. These can be controlled via [[conftool]] as well, including with the <code>depool</code> and <code>pool</code>utilities. This is documented at [[LVS#Etcd as a backend to Pybal (All of production)]].

== Re-pooling ==

Using the same example host from above, re-pooling the hosts consists of a similar command from the de-pooling:

<code>
$ sudo confctl select dc=<dc>,cluster=<cluster-name>,name=cp*** set/pooled=yes
</code>

Alternatively, ssh into the server and run

<code>
$ sudo -i pool
</code>

[[Category:How-To]]
[[Category:Runbooks]]