Terra
03-03-1999, 04:58 PM
CONTINUED from www.aota.net/ubb/Forum4/HTML/000086.html (http://www.aota.net/ubb/Forum4/HTML/000086.html)
We have received the green light from UUnet upstream to begin the Phase 2 upgrades...
Below is a brief itinerary of what Phase 2 entails...
2/16:done: Finish up stress testing on new kernel and server
2/17:done: Recompile all low-level network tools and shared glibc2 libraries
2/18:done: Finish upgrading and converting all DNS Bind entries 4.9.4 to 8.1.2 // finish setup and testing of eth0:2-254 aliasing for new C-Block
2/19:done: Plug up new server 'six.futurequest.net' to UUnet and reconfigure for full C-Block
2/20: ARRrrrggghhhhh, Internic has thrown a curve ball by delaying the registration of 'ns2.futurequest.net' and 'ns3.futurequest.net'... Guess it's our turn to throw our glove in the ring with Internic... I cannot complete the move successfully until these new hosts are registered... This was started 2 weeks ago, and today I find they have put it in their manual queue... gggggrrrrrrrrrrr!
2/22:Internic just approved ns2.futurequest.net, still waiting for ns3.futurequest.net
2/23:ns3.futurequest.net just got approved
2/24:waiting for DNS/RARP reverse delegations to be mapped to new nameservers
2/26:done:Move 1 (low bandwidth sites over) and test
2/26:done:Move 2 (large bandwidth sites) and test
2/27:cleanup nasty mess left behind from SprintLink
2/28:done:Move 15 (low bandwidth sites over) and test
2/28:done:Move 5 (large bandwidth sites) and test
3/01: Watch operations and perform more sanity checking
3/03:almost:In coordination with ITC DeltaCom, we now have makeshift RARP reverse resolves, we are still waiting on ARIN.net to authorize the final changes... For now ITC has agreed to do our 'in-arpa' till ARIN.net comes through...
3/03:done:Update all domains Internic Templates to reflect the new nameserver information... (Thanks Deb!)
3/04:done:Rewrite the new account setup routines / run a batch of 12 and observe
3/??: Start moving the rest over
3/??: Pull 'old' TAZ offline, retrofit with Linux 2.2.1, and rechristen it as (new) 'taz.futurequest.net' for the T-3...
**New Section: Planned (Major) Software Upgrades**
2/17:done:RedHat 5.2 (base only)
2/18:done:glibc2 (fast compile)
2/20:done:Bash 2.02.1
2/20:done:Python 1.5.1
2/21:done:Perl 5.005_02 (Seeing if I can maintain, in production usage, 5.004_04 or not)
2/21:done:recompile all installed Perl 5.004_04 modules to new 5.005_02 binary compatability synchronizing both code trees... (If I missed any, please let me know)
2/22:done:Apache 1.3.4
2/22:done:PHP 3.0.6 (Apache 1.3.4 primary engine pool)
2/25:done:Apache mod_SSL 2.2.3-1.3.4 (My brain hurts!)
3/03:done:PHP 3.0.7 (Apache 1.3.4 primary engine pool)
3/03:done:MySQL 3.22.19a-gamma
3/04:done:recompile Perl DBI::DBD (MySQL) Modules
3/12:done:Gandalf 2.0 (Thawte CERT registrations)
3/??::PHP 3.0.6 (Apache 1.3.4 backend engine pool)
3/??::Apache mod_perl (backend engine pool)
##?/??::QMail 1.03 (possible, if have time)
##why upgrade what isn't broken...
**END Major Software Upgrades**
Most of your visitors will not notice that the move has taken place, except for faster response times... http://www.aota.net/ubb/wink.gif
On 3/?? (If all testing goes A-OK) then for a period of 4 hours, all passwords will be disabled on the old server (for the domains being moved)...
EMail should all flow to the new mail server as well...
If you find that you get an invalid login, then either wait for the DNS propagation to take place (3 hours or less), or use our new IP to login with: 209.192.41.100
Our new C-Block is: 209.192.41.x
There will be a total of 6 Phases that our upgrades will go through, over the next 4 to 6 months, as we are on track to our final destination of the OC-12 NOC...
I will post more information concerning Phase 2 as it becomes available to me...
--
Andrew Gillespie
Systems Administrator
FutureQuest.net
[This message has been edited by ccTech (edited 03-03-99).]
[This message has been edited by ccTech (edited 03-05-99).]
[This message has been edited by ccTech (edited 03-13-99).]
We have received the green light from UUnet upstream to begin the Phase 2 upgrades...
Below is a brief itinerary of what Phase 2 entails...
2/16:done: Finish up stress testing on new kernel and server
2/17:done: Recompile all low-level network tools and shared glibc2 libraries
2/18:done: Finish upgrading and converting all DNS Bind entries 4.9.4 to 8.1.2 // finish setup and testing of eth0:2-254 aliasing for new C-Block
2/19:done: Plug up new server 'six.futurequest.net' to UUnet and reconfigure for full C-Block
2/20: ARRrrrggghhhhh, Internic has thrown a curve ball by delaying the registration of 'ns2.futurequest.net' and 'ns3.futurequest.net'... Guess it's our turn to throw our glove in the ring with Internic... I cannot complete the move successfully until these new hosts are registered... This was started 2 weeks ago, and today I find they have put it in their manual queue... gggggrrrrrrrrrrr!
2/22:Internic just approved ns2.futurequest.net, still waiting for ns3.futurequest.net
2/23:ns3.futurequest.net just got approved
2/24:waiting for DNS/RARP reverse delegations to be mapped to new nameservers
2/26:done:Move 1 (low bandwidth sites over) and test
2/26:done:Move 2 (large bandwidth sites) and test
2/27:cleanup nasty mess left behind from SprintLink
2/28:done:Move 15 (low bandwidth sites over) and test
2/28:done:Move 5 (large bandwidth sites) and test
3/01: Watch operations and perform more sanity checking
3/03:almost:In coordination with ITC DeltaCom, we now have makeshift RARP reverse resolves, we are still waiting on ARIN.net to authorize the final changes... For now ITC has agreed to do our 'in-arpa' till ARIN.net comes through...
3/03:done:Update all domains Internic Templates to reflect the new nameserver information... (Thanks Deb!)
3/04:done:Rewrite the new account setup routines / run a batch of 12 and observe
3/??: Start moving the rest over
3/??: Pull 'old' TAZ offline, retrofit with Linux 2.2.1, and rechristen it as (new) 'taz.futurequest.net' for the T-3...
**New Section: Planned (Major) Software Upgrades**
2/17:done:RedHat 5.2 (base only)
2/18:done:glibc2 (fast compile)
2/20:done:Bash 2.02.1
2/20:done:Python 1.5.1
2/21:done:Perl 5.005_02 (Seeing if I can maintain, in production usage, 5.004_04 or not)
2/21:done:recompile all installed Perl 5.004_04 modules to new 5.005_02 binary compatability synchronizing both code trees... (If I missed any, please let me know)
2/22:done:Apache 1.3.4
2/22:done:PHP 3.0.6 (Apache 1.3.4 primary engine pool)
2/25:done:Apache mod_SSL 2.2.3-1.3.4 (My brain hurts!)
3/03:done:PHP 3.0.7 (Apache 1.3.4 primary engine pool)
3/03:done:MySQL 3.22.19a-gamma
3/04:done:recompile Perl DBI::DBD (MySQL) Modules
3/12:done:Gandalf 2.0 (Thawte CERT registrations)
3/??::PHP 3.0.6 (Apache 1.3.4 backend engine pool)
3/??::Apache mod_perl (backend engine pool)
##?/??::QMail 1.03 (possible, if have time)
##why upgrade what isn't broken...
**END Major Software Upgrades**
Most of your visitors will not notice that the move has taken place, except for faster response times... http://www.aota.net/ubb/wink.gif
On 3/?? (If all testing goes A-OK) then for a period of 4 hours, all passwords will be disabled on the old server (for the domains being moved)...
EMail should all flow to the new mail server as well...
If you find that you get an invalid login, then either wait for the DNS propagation to take place (3 hours or less), or use our new IP to login with: 209.192.41.100
Our new C-Block is: 209.192.41.x
There will be a total of 6 Phases that our upgrades will go through, over the next 4 to 6 months, as we are on track to our final destination of the OC-12 NOC...
I will post more information concerning Phase 2 as it becomes available to me...
--
Andrew Gillespie
Systems Administrator
FutureQuest.net
[This message has been edited by ccTech (edited 03-03-99).]
[This message has been edited by ccTech (edited 03-05-99).]
[This message has been edited by ccTech (edited 03-13-99).]