Some more discussion:

Busmon actually only needs to store 40 integers at any given time. It seems extra-silly to set up a whole new host just for that.

The motivation for housing this on its own host remains though in mediawiki's hard dependency on memcached. If a new admin is trying to debug and fix busmon and in so doing, takes down memcached, that admin would have unknowningly taken down the wiki as well! That's reason enough to separate the service.

Fun fact: pkgdb also uses memcached on app0{3,4} even though its not documented in the infra-docs/. fas also runs its on memcached on fas0{1,2,3}.

Could we just stand up an instance on busgateway01 for this?

I suppose it could be pretty small memory wise?

That sounds fine to me. I can most likely set it up tomorrow if there are no objections.

This is working now. memcached is up on busgateway01 and busgateway01.stg.

Unrelated, I have a new release of busmon rpms that optimize the way it behaves on the bus that haven't been deployed yet, but its a relatively simple change that should affect the ticket. Closing!