1175845 - Split bugbot into different instance per network

Status: NEW

(Bugzilla :: bugzilla.org, enhancement)

Description

[Teemu Mannermaa (:wicked)]

While having a single instance is good for various reasons and supybots do have decent multi network support, recently there has been more and more problems due to bugbot been shared with Freenode, Gnome and Mozilla networks. Specifically, this is to address following problems:

 - On Freenode, bugbot nick is owned by different bot so our bugbot needs to have buggbot nick there and this has complicated things a bit. (Mostly resulting in him not been nickserv authed there correctly but also adds nickserv spam.)
 - If bugbot is on channel that has same name on two different networks, all configuration is shared between them. This means bugbot will bugspam the same bugs there. For example, this makes it impossible to have #bugbot channel on two networks and have different bugspam/config there.
 - On Gnome they would like to have BGO as their default Bugzilla, which is totally understandable. Unfortunately, there doesn't seem to be network level default in supybot so all their channels need to overrides setup (and there are lot of those).
 - Also on Gnome, they have a sysadmin team that could use shell access for the bot to be able to kick him as needed and having a split instance would allow us to give that to them only for their instance.

Therefore we probably might want to split bugbot into three different instances each inhabiting different network. They would still all get same incoming bug spam. Before this can happen, the bugbot needs to more to the new server so we can put more load on it.

Opionions? Objections? Additional problems? Different ways to handle them?

Comment 1

[Dave Miller [:justdave]]

I apparently never managed to see this bug before now, but we can take care of some of those.

(In reply to Teemu Mannermaa (:wicked) from comment #0)

Before this can happen, the bugbot needs to more to the
new server so we can put more load on it.

This part happened already, it's got an entire server to itself now in Linode.

(In reply to Teemu Mannermaa (:wicked) from comment #0)

• On Freenode, bugbot nick is owned by different bot so our bugbot needs to
  have buggbot nick there and this has complicated things a bit. (Mostly
  resulting in him not been nickserv authed there correctly but also adds
  nickserv spam.)

This one can be solved by upgrading supybot to one of its forks. Limnoria(sp?) handles multi-network pretty well, and has separate settings for each network.

• If bugbot is on channel that has same name on two different networks, all
  configuration is shared between them. This means bugbot will bugspam the
  same bugs there. For example, this makes it impossible to have #bugbot
  channel on two networks and have different bugspam/config there.

I'm not sure if Limnoria's multi-network support includes separate channel configs or not, we'd need to look into it,

• Also on Gnome, they have a sysadmin team that could use shell access for
  the bot to be able to kick him as needed and having a split instance would
  allow us to give that to them only for their instance.

Since its on a box by itself now, I've got no problem giving someone shell access to kick it.

Therefore we probably might want to split bugbot into three different
instances each inhabiting different network. They would still all get same
incoming bug spam. Before this can happen, the bugbot needs to more to the
new server so we can put more load on it.

Only thing I can think of that might be an issue is that bot actually removes the email from the mailbox when it reads it, so we'd need to actually create different mailboxes for each instance, and put them all on a group alias under the main incoming email address or something. If we can do that, splitting them would probably work fine.

Comment 2

[Dave Miller [:justdave]]

Bugbot has been upgraded to the 202211 Limnoria snapshot. The plugin just got a massive overhaul to make it work with Python 3 (which Limnoria now requires)

It currently is handling BMO only (though it's still receiving email from RedHat it looks like, but just ignoring it).

The whole thing basically died when our channel got booted from Freenode, and I just recently got it working on Libera.

If anyone wants their network added back to it let me know.

Sounds like GNOME could use their own instance still regardless of everything else... I updated the docs in the readme, it should be easier to set up now, too. I'm working on getting it added to the Limnoria plugin repo.