And this has essentially* been completed as of 2014-03-22T17:59:10-0700. *all the data migrations, etc. completed, and as long as one isn't accessing direct via IP address or one very obscure non-canonical DNS name, all should be working and fine and available again as per "normal". I'm also happy to report that the host is again in a much higher availability location and with very good bandwidth. Thanks again to Jim Stockford for securing the location for us.
From: "Michael Paoli" Michael.Paoli@cal.berkeley.edu Subject: disruptions to some (mostly non-production) BALUG services Date: Sat, 22 Mar 2014 17:38:36 -0700
And, back we go again - starting NOW. For the most part, if you're not making changes or using a long-running connection (e.g. ssh session), you probably won't notice. If you do make changes, those CHANGES MAY NOT BE MIGRATED, effective NOW, until the migration is completed. I'm guestimating that will be less than or approximately one hour's time total. I'll update notification when the migration is completed.
This WILL NOT impact: www.balug.org balug.org (itself) BALUG's lists It WILL impact: many non-production services and some ancillary production services, e.g.: archive.balug.org www.archive.balug.org wiki.balug.org www.wiki.balug.org secure.balug.org Technical details: If it's on 198.144.194.234 it will be impacted (IP will change). rsync ... reconfigure & boot target ... DNS