Currently the pybal_config backend of cache_misc is defined as randomized over multiple hosts using the hiera list of puppetmaster directly. This should be moved to an LVS service exposing a singular internal service hostname.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| cache_misc: pybal_config: use puppetmaster1001.eqiad only | operations/puppet | production | +1 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | BBlack | T147844 Standardize varnish applayer backend definitions | |||
| Resolved | BBlack | T147847 Move pybal_config to an LVS service |
Event Timeline
Comment Actions
I don't think it uses it directly. LVS/pybal talks directly to etcd, whereas this is just an HTTP view of the same data.
Comment Actions
(well, beyond that, I think it's exposing the old text files even, not the new etcd data?).
Comment Actions
@BBlack you are correct saying it isn't used by pybal anymore, but incorrect when saying it's exposing the old text files: the current files are generated from etcd.
Comment Actions
Change 315531 had a related patch set uploaded (by BBlack):
cache_misc: pybal_config: use puppetmaster1001.eqiad only
Comment Actions
See patch above. I think we can skip over the LVS bit here, until some later date when we have more than one backend defined per-datacenter. We also can't/shouldn't really be using mixed eqiad+codfw backends in this place today (that's for later when cache_misc properly supports it at all).
Comment Actions
Change 315531 merged by BBlack:
cache_misc: pybal_config: use puppetmaster1001.eqiad only