> > > > 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. 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. A third approach would be to let all servers choose their own UUID, but have the load-balancer re-write the UUID in outbound feed requests. You can do this with a BigIP. I don't know what LB equipment we're using locally. (I'm assuming you can also do something like this with Apache, Stephen?) I'm sure there's a fourth approach that I'm missing, but I can't think of it right now. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
