This is supposed to be a VM with buster, to host testreduce (nodejs, formerly on scandium, the parsoid test host on real hardware).

More details on T257906

CPU and disk requirements still to be determined. CCing @SubrahamanyamVarma

@Dzahn please note that my handle is @ssastry - I know it is confusing with multiple subbus and almost identical first names. Removing the other subbu from the task.

So, here is how rt-testing works. There is a testreduce server which is nodejs code that needs a connection to a mysql db. There are testreduce clients that run nodejs code to fetch page titles from the server and then run custom code. In the rt-testing use-case, it runs bin/roundtrip-test.js code form the parsoid repo which contacts Parsoid API to do a bunch of work on its behalf, runs some diffs, analyzes diffs and computes a test score and sends the test score with the title back to the testreduce server.

The testreduce server, testreduce clients and Parsoid API can all run on different servers. So, multiple VMs can run testreduce clients for example .. they just ping the server periodically for work, and so, we control new test runs by updating the testreduce server test run control file.

In the current hardware setup, everything runs on scandium. And, the most resource intensive part of the work is Parsoid API itself. The testreduce clients are less resource intensive (cpu-wise and maybe memory wise too). So, as long as scandium runs Parsoid API to respond to testreduce client requests, we can set up this other VM (or VMs) to run the server and clients. They can all be on the same single VM. The # of testreduce clients we can run is bounded by scandium's response rate and resource usage. Right now, we run 28 on scandium. I imagine, we can probably run 32 if we move testreduce scripts off scandium.

In T257940#6305264, @ssastry wrote:

@Dzahn please note that my handle is @ssastry - I know it is confusing with multiple subbus and almost identical first names. Removing the other subbu from the task.

I knew that but for some reason thought you actually changed your full name in phab :p

Change 612971 had a related patch set uploaded (by Dzahn; owner: Dzahn):
[operations/dns@master] add IP for testreduce1001

https://gerrit.wikimedia.org/r/612971

Change 612971 merged by Dzahn:
[operations/dns@master] add IP for testreduce1001

https://gerrit.wikimedia.org/r/612971

Change 612983 had a related patch set uploaded (by Dzahn; owner: Dzahn):
[operations/puppet@production] DHCP/partman: add MAC for testreduce1001

https://gerrit.wikimedia.org/r/612983

Change 612983 merged by Dzahn:
[operations/puppet@production] DHCP/partman: add MAC for testreduce1001

https://gerrit.wikimedia.org/r/612983

Change 613201 had a related patch set uploaded (by Dzahn; owner: Dzahn):
[operations/puppet@production] site: add testreduce1001 with insetup role

https://gerrit.wikimedia.org/r/613201

Change 613201 merged by Dzahn:
[operations/puppet@production] site: add testreduce1001 with insetup role

https://gerrit.wikimedia.org/r/613201

Change 613278 had a related patch set uploaded (by Dzahn; owner: Dzahn):
[operations/puppet@production] parsoid: create new role to install just testreduce vd-server

https://gerrit.wikimedia.org/r/613278

Change 613278 merged by Dzahn:
[operations/puppet@production] parsoid: create new role to install just testreduce

https://gerrit.wikimedia.org/r/613278

Mentioned in SAL (#wikimedia-operations) [2020-10-21T21:38:23Z] <mutante> testreduce1001 assigned 2 more GBs of RAM - rebooting (T257940, T257906)

Mentioned in SAL (#wikimedia-operations) [2020-10-22T22:42:16Z] <mutante> ganeti1001 - adding 2 more vcpus to VM testreduce1001 - T257940