I was poking around in netbox and noticed the tenant feature being used to group things for fr-tech and OIT. I was wondering if this is something we can also do for Cloud Services or if that would not be nice or easy because our netbox tracked hardware is not as isolated from the rest of eqiad and codfw as the hardware for those groups are.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | aborrero | T208576 Netbox: Usage guidelines for WMCS | |||
| Declined | None | T245711 Add tenant for Cloud Services? |
Event Timeline
Comment Actions
WMCS hosts are in the production VLANs, managed by the production puppet etc. Practically speaking, we use tenants to exclude fr-tech/OIT/RIPE hosts from reports (that e.g. alert if an active host is not present in PuppetDB or vice-versa), and will likely also use it to exclude them from the in-progress IP assignment/bootstrapping work. If we were to assign a tenant to those hosts, we'd have to special-case it pretty much everywhere to treat it like the "production" tenant (which is now the "null" tenant).
I think it'd be better to keep the tenant feature for infrastructure that's really a separate "tenant" in ours, i.e. things that we are hosting but not managing by any production infrastructure. I don't think that's the case with WMCS so far...
Comment Actions
Thanks for that feedback @faidon. I am not surprised by the way that these lines are being drawn, but I thought it would be worth checking again to see if there was any difference from the past discussions. We will wait patiently for a future where some tagging/grouping functionality can be used besides hostname prefix searching for teams like us, Search, etc who manage hardware within the larger undifferentiated pool of shared resources.