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


From Wikitech-static
< Portal:Toolforge
Revision as of 18:25, 20 February 2018 by imported>Quiddity (added Category:Toolforge using HotCat)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

The list of Toolforge nodes. This documentation provides information about what kind of nodes exists in the cluster, what every node does and a prospective list of canary server for common operations like testing new stuff.

Complete list of nodes

The source of trust for this information is at

Take this list as an example, and refer to the source of trust for actual/current data.

Purpose of nodes

Explanation of what each type of node is.

bastion nodes

Servers meant to allow access to the clusters for users using SSH. You can submit your grid jobs from here.

They are not meant to run any actual workload. There are usually like 3 of them.

Nodes are like:

GridEngine nodes

Nodes that run GridEngine and are the pool to run standard Toolforge jobs workloads.

There should be like 20 or 30 of them.

  • Nodes are like:
  • Master nodes are like

Kubernetes nodes

Nodes that run kubernetes and hold the k8s workloads (pods).

There should be like 10 or 20 of them.

  • Nodes are like:
  • Master nodes are like:
  • etcd nodes are like:

PAWS nodes

Nodes that run the PAWS deployment (using kubernetes). For several reasons, PAWS doesn't share the main k8s deployment.

There should be like 10 or 20 of them.

  • Nodes are like:
  • Master nodes are like:

Web nodes

Nodes that acts as frontend web hosts for tools in Toolforge.

There should be like 10 or 20 of them.

  • Generic nodes are like:
  • Those using lighttpd are like:
  • General web proxy nodes:
  • Static content nodes:

Docker nodes

These nodes are meant to build and distribute docker containers.

There should be like 3 or them.

  • Builder nodes are like:
  • Docker registry nodes are like:

Elastic nodes

TODO: fill me. Deployment of elastic?

There should be like 3 nodes.

  • Nodes are like:

Flannel nodes

Nodes related to the etcd deployment for the flannel network overlay.

There should be like 3 nodes.

  • Nodes are like:

checker nodes

TODO: fill me

misc nodes

Some misc nodes.

  • Clush master, control of the whole cluster using Clustershell:
  • Cron master, run cron jobs submitted by tools users:
  • SMTP email for the cluster:
  • DEB package builder:
  • Prometheus deployment nodes:
  • Redis nodes:
  • Misc services nodes (aptly and others):
  • TODO: fill me:

Canary nodes

A pre-elected list of one node of each type you can use to test stuff before deploying changes to the whole cluster.

Depending on the test or task you are doing, you may need to craft a different list:

  • Different OS (Ubuntu trusty, Debian jessie, Debian stretch)
  • By Linux kernel version
  • By different workload, usage or general load
  • Attending to other criteria

See also

Some related information.