[EMAIL PROTECTED] wrote: >>>>> Why not just disable the feed on all but the primary? Since it's >>>>> 100% cacheable it doesn't seem like a big deal. >>>> In this example, how would you determine the webserver that is the >>>> primary? >>> Umm, I don't know... are we having the notion of the authoritative >>> ultimate source of knowledge amongst a group of mirrors? If not, >>> then I guess never mind. >> It's not just mirrors here, but a bunch of servers which are merely >> load-balanced, like the ones we already have. They're effectively a single >> server, which means that none is in any sense a primary, nor is anyone "at >> the front" sufficiently to capture all the feed requests. > > This is the nuance that I was trying to tease out. Unfortunately, the > way I asked the question implied that I didn't know the answer. > > This is the typicial way that servers are configured behind a load > balancer. If we expect all servers to be identical, then yes, we'll > need a way to replicate the UUID across all servers in the pool.
In my mind, it shouldn't be a problem to sync the repository configuration across all the servers. You would want them to all have the same metadata, etc. anyway. > Another approach would be, as Stephen suggested, to have one server > known as the primary to the administrators. We'd have to re-direct all > feed/info requests to that server in the pool. Only the feed really matters. -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
