We should make it easy to reference all LVS interface addresses within a given DC from a ferm rule in puppet, somehow in some standard way with our network module and data constants and slicing.
We can start on this today as IPv4 only to unblock the known use-case for analytics, then add the IPv6es being worked on in T179025 + T179026 aftwerwards.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T180971 Create LVS endpoint for druid-public-overlord (for oozie job indexing) | |||
| Open | None | T179027 Puppetize LVS interface IP sets per-DC for easy use in ferm rules | |||
| Resolved | elukey | T176223 Create Druid public cluster such AQS can query druid public data | |||
| Resolved | Ottomata | T177511 LVS for Druid |
The swap of Traffic for Traffic-Icebox in this ticket's set of tags was based on a bulk action for all such tickets that haven't been updated in 6 months or more. This does not imply any human judgement about the validity or importance of the task, and is simply the first step in a larger task cleanup effort. Further manual triage and/or requests for updates will happen this month for all such tickets. For more detail, have a look at the extended explanation on the main page of Traffic-Icebox . Thank you!