mirror sites with multiple hosts behind one name should be probed more completely
Bug #221866 reported by
LaMont Jones
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
There are two configurations that the mirror prober does not handle well, since it assumes that one entry == one machine:
1) multiple A RRs for the same name
- this is almost always multiple hosts, and each should be probed independently, any failure should propagate up.
2) multiple hosts behind the same (virtual) IP
- This is a case where the mirror registrant needs to be able to have either:
- multiple registrations that publish as one entry in the +*mirrors pages, or
- one entry with multiple backend hosts for launchpad to check.
| affects: | launchpad-foundations → launchpad-registry |
| Changed in launchpad-registry: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| tags: | added: mirror |
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
To post a comment you must log in.
An example of this is the NZ citylink mirror, which uses BGP or similar routing tricks to be in both SF and NZ, and only NZ hosts talk to the NZ end; so this is a case of 2) - publish one entry, and check multiple backends.