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


From Wikitech-static
< Portal:Toolforge‎ | Admin
Revision as of 14:21, 29 October 2018 by imported>Arturo Borrero Gonzalez (→‎Architecture: add note about how puppet code works for toolforge-stretch)
Jump to navigation Jump to search

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):

  • tools-services-01
  • tools-services-02

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.


updatetools is a Python script that updates tools and maintainers information to be used by (source code available at tool-admin-web).

It gets a list of tools (accounts starting with "tools."), reads their .description and 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 users table.

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.

apt repository

TODO: fill me. Are we going to use the aptly repo in the new toolforge version?


TODO: fill me.

Admin operations

TODO: fill me.

See also