LUCI: multiple machines for one bot

[Benny Siegert]

Hi!

For the netbsd-arm64-bsiegert builder, there used to be two machines for capacity and redundancy. Now, for LUCI, I tried running swarming bots on both machines with the same bot ID, .cert and .key file. However, it appears as a single entity on https://chromium-swarm.appspot.com/bot?a=true&id=netbsd-arm64-bsiegert.

I assume bot IDs need to be unique for LUCI, so I would need to add a second bot into the same pool. Is that right?

—
Benny

[Dmitri Shuralyov]

Hi Benny,

Yes, the LUCI bot ID indeed must be unique per running bot instance. The certificate used in issue #63614 used "netbsd-arm64-bsiegert" as the hostname, which requires the bot ID to be either "netbsd-arm64-bsiegert" exactly, or "netbsd-arm64-bsiegert--{suffix}" (two dashes after the hostname) for some suffix. So you could name your two instances "netbsd-arm64-bsiegert--01" and "netbsd-arm64-bsiegert--02" or another suffix that you find works well. 

Thanks,
Dmitri

[Benny Siegert]

> Yes, the LUCI bot ID indeed must be unique per running bot instance. The certificate used in issue #63614 used "netbsd-arm64-bsiegert" as the hostname, which requires the bot ID to be either "netbsd-arm64-bsiegert" exactly, or "netbsd-arm64-bsiegert--{suffix}" (two dashes after the hostname) for some suffix. So you could name your two instances "netbsd-arm64-bsiegert--01" and "netbsd-arm64-bsiegert--02" or another suffix that you find works well.

That’s exactly what I need. I wasn’t aware of the suffix rule. Thank you.

—
Benny