Team drive #7 k=800-1001 n=600K-1M

[gd_barnes]

Originally Posted by mdettweiler

Oh, duh! I just remembered, we already have a G7000. Never mind, looks like my grand plan for lining up port 7000 with Drive #7 won't work.

We'll do G3000 instead, which really is empty.

You've got me baffled now. We'll do G3000 for what? The non-top-5000 work for IB7000 on the 12th drive? If so, that's fine. The idea is to minimize the # of changes while still making everything as clear as possible for what we will eventually end up with.

Max, you're driving the server changes but I'll still offer my thoughts: Because this drive server is already on my machine, I'm assuming that we don't want to change it.


Gary

[mdettweiler]

Originally Posted by gd_barnes

You've got me baffled now. We'll do G3000 for what? The non-top-5000 work for IB7000 on the 12th drive? If so, that's fine. The idea is to minimize the # of changes while still making everything as clear as possible for what we will eventually end up with.

Max, you're driving the server changes but I'll still offer my thoughts: Because this drive server is already on my machine, I'm assuming that we don't want to change it.


Gary

Okay, to clarify: the current G4000 will soon be moved to G3000. That is so that when we move IB4000 to your server eventually, its port # doesn't clash with an eisting server.

As I said above, it's somewhat of an arbitrary decision whether to move IB4000 or G4000 to make room for the other. In this case I chose G4000 since there's less middlemen to deal with in just switching over a port that I have direct access to.

[gd_barnes]

Originally Posted by mdettweiler

Okay, to clarify: the current G4000 will soon be moved to G3000. That is so that when we move IB4000 to your server eventually, its port # doesn't clash with an eisting server.

As I said above, it's somewhat of an arbitrary decision whether to move IB4000 or G4000 to make room for the other. In this case I chose G4000 since there's less middlemen to deal with in just switching over a port that I have direct access to.

It's arbitrary but why make it more difficult than it needs to be? Why not just leave G4000 as it is with this drive? Then later on change IB4000 to G3000 (or whatever).

That's only 1 change instead of 2 changes. Shouldn't we be doing less changes? Why force people on this drive (namely Ian) to change all of their machines unless it is really needed. The people on the 5th drive (mostly me) will have to change all of their machines regardless of whatever is done.

I'm trying to understand the reasoning behind changing both instead of only changing one.


Gary

[mdettweiler]

Originally Posted by gd_barnes

It's arbitrary but why make it more difficult than it needs to be? Why not just leave G4000 as it is with this drive? Then later on change IB4000 to G3000 (or whatever).

That's only 1 change instead of 2 changes. Shouldn't we be doing less changes? Why force people on this drive (namely Ian) to change all of their machines unless it is really needed. The people on the 5th drive (mostly me) will have to change all of their machines regardless of whatever is done.

I'm trying to understand the reasoning behind changing both instead of only changing one.


Gary

Aha, I see what you're confused about now. The way we're going to be switching things over, everyone currently on an IB port won't have to do anything at all during the switchover. The key to all of this is the domain name, noprimeleftbehind.net. Right now, that points to David's servers. But when we switch things over, we'll change it so it points to your servers instead. Thus, aside from a hopefully brief downtime during the changeover (which can be mitigated by using large caches on clients), there should be essentially no ill effect on the IB clients other than that of a normal IP address change.

Now you see why it's somewhat arbitrary? None of the clients will need to move at all (and at the very least might need to have their DNS cache flushed to account for the IP change), except for the ones on clashing port numbers, which we're moving ahead of time so that we don't have to deal with it later when we're doing a million things related to the switchover.

[gd_barnes]

Originally Posted by mdettweiler

Aha, I see what you're confused about now. The way we're going to be switching things over, everyone currently on an IB port won't have to do anything at all during the switchover. The key to all of this is the domain name, noprimeleftbehind.net. Right now, that points to David's servers. But when we switch things over, we'll change it so it points to your servers instead. Thus, aside from a hopefully brief downtime during the changeover (which can be mitigated by using large caches on clients), there should be essentially no ill effect on the IB clients other than that of a normal IP address change.

Now you see why it's somewhat arbitrary? None of the clients will need to move at all (and at the very least might need to have their DNS cache flushed to account for the IP change), except for the ones on clashing port numbers, which we're moving ahead of time so that we don't have to deal with it later when we're doing a million things related to the switchover.

That's way too confusing to me. If you can make it where people have to change little or nothing on their machines, that sounds good to me.

Based on that, I'm assuming that anyone currently connecting to my current servers with the no-IP address will not necessarily have to change to the noprimeleftbehind address.

If that is the case, it will be a good idea to inform everyone to eventually make that change so that we can get rid of all of these port forwarding (or whatever they would be called) things that are internally in the servers.

[mdettweiler]

Originally Posted by gd_barnes

That's way too confusing to me. If you can make it where people have to change little or nothing on their machines, that sounds good to me.

Based on that, I'm assuming that anyone currently connecting to my current servers with the no-IP address will not necessarily have to change to the noprimeleftbehind address.

If that is the case, it will be a good idea to inform everyone to eventually make that change so that we can get rid of all of these port forwarding (or whatever they would be called) things that are internally in the servers.

First of all, no, nobody on nplb-gb1.no-ip.org will have to change (except for G4000 which we'll be moving as previously discussed). After we've completed the move, nplb-gb1.no-ip.org will be synonymous with noprimeleftbehind.net.

As for port forwarding, I think you're a little confused; port forwarding is always necessary in order to put a port number online from a machine behind a router. Perhaps you're thinking of a port # redirect? We don't have any of those right now on the GB servers, and don't have any particular plans or needs to use any.

[gd_barnes]

Yeah, port redirect is what I meant.

What I was attempting to imply was this: Isn't there some sort of "quasi redirect" that is needed to "tell" the server that nplb-gb1.no-ip.org will be synonymous with noprimeleftbehind.net? If not, how does the server "know" that they are synonymous?

[mdettweiler]

Originally Posted by gd_barnes

Yeah, port redirect is what I meant.

What I was attempting to imply was this: Isn't there some sort of "quasi redirect" that is needed to "tell" the server that nplb-gb1.no-ip.org will be synonymous with noprimeleftbehind.net? If not, how does the server "know" that they are synonymous?

The server won't need to "know" that they're synonymous. It will simply be that nplb-gb1.no-ip.org will point to the same IP address as noprimeleftbehind.net.

Similarly, IronBits' various domains all point to his IP address, which is why you can (say) point an LLRnet client to ironbits.net port 5000 or free-dc.org port 5000 and still get our IB5000 server. However, the reason why he has different websites on those addresses is because he put a "quasi redirect" of sorts in to tell his web server which page to answer with depending on which domain a browser is going to. Essentially, things like this with multiple domains pointing to the same IP address are considered synonymous unless otherwise noted.

[gd_barnes]

All I can say is: Wow, that's cool that no one will have to change their LLRnet clients!

Personally I would recommend that everyone point to noprimeleftbehind.net for the future gb servers but if they don't have to change them from the no-IP address, then I guess it really doesn't matter.

Thanks for clarifying.

[MyDogBuster]

I'm going to need some pairs loaded on GB4000. Down to < a weeks worth.
Max only loaded n=10K worth the last time and it went fast. Maybe 20k would be better.

[gd_barnes]

Reserving n=730K-740K for port G4000. I'll round it out and we'll load an n=20K range next go around.