You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org
This page is currently a draft.
More information and discussion about changes to this draft on the talk page.
This page contains information regarding the services that are provided internally to Toolforge nodes.
The services run from a single VM (with a spare one already provisioned for maintenance and disaster recovery purposes):
The active one is determine by the value of
role::toollabs::services::active_host in Hiera.
NOTE: in new toolforge-stretch, the puppet role is role::wmcs::toolforge::services and the relevant hiera key is profile::toolforge::services::active_node.
It gets a list of tools (accounts starting with "tools."), reads their
toolinfo.json files and adds it to the
tools table in the
toollabs_p database. Maintainer information is retrieved by getting all users that belong to the tool's group and using
getpwnam() to retrieve user information, which then gets added to the
This script runs, as a service, from the active
tools-services-* server, and wakes up every 120 seconds to populate the tables with new data.
The database in use is
tools.labsdb which is
TODO: fill me. Are we going to use the aptly repo in the new toolforge version?
This daemon is used to restart grid jobs in case they are found not running. Users (tools) can instruct which jobs to monitor to the daemon via a
The daemon itself will log to
Services nodes are grid submit nodes apparently. We don't know why yet or if this can be replaced/deleted/deprecated.
TODO: fill me.