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.orgbalug.org (itself)
BALUG's lists
It WILL impact:
many non-production services and some ancillary production services,
e.g.:
archive.balug.orgwww.archive.balug.orgwiki.balug.orgwww.wiki.balug.orgsecure.balug.org
Technical details:
If it's on 198.144.194.234 it will be impacted (IP will change).
rsync ... reconfigure & boot target ... DNS
Due to needed physical host relocation (not sure of precise timing),
I'm expecting we may have some disruptions and/or non-continuity of
service for some BALUG services. Guestimated the impact may be on the
order of some hour(s) or (probably) less, or may involve some
discontinuity/inconsistencies of service (e.g. updates/changes may not
propagate to new host location).
I'll provides updates when I'm reasonably able to, however note at the
present time:
THESE DISRUPTIONS MAY OCCUR WITHOUT FURTHER ADVANCE NOTICE.
In "worst case" I'll be able to provide update when the dust is settled
and the move more-or-less completed, and in any case I'll provide update
when we can expect things are relatively settled and not as likely to
generally suffer more disruptions (mostly notably services should be
restored to much more consistent again, though availability probably
won't be as high as the current colo setup, as host won't be going to a
colo).
This WILL NOT impact:
www.balug.orgbalug.org (itself)
BALUG's lists
It WILL impact:
many non-production services and some ancillary production services,
e.g.:
archive.balug.orgwww.archive.balug.orgwiki.balug.orgwww.wiki.balug.orgsecure.balug.org
Technical details:
If it's on 208.96.15.254 it will be impacted (IP will change).
FYI,
I'm planning bit of maintenance and short outage for host "vicki" and its
VMs this PM
(after 5:00 P.M., probably sometime after 6:00 P.M.).
Outage should be relatively short (estimated less than 5 minutes)
This WILL NOT impact:
www.balug.orgbalug.org
BALUG's lists
It WILL impact:
many non-production services and some ancillary production services,
e.g.:
archive.balug.orgwww.archive.balug.orgwiki.balug.orgwww.wiki.balug.orgsecure.balug.org
Mike Higashi, et. al., (& CCing admin list, as there's no reason not to)
You'd earlier mentioned bit about BALUG and publicity, etc. Although
it's not exactly highly current, we *do* have a wiki page that covers
that relatively well. Sort of a "how to", and what to cover (and not
cover), and how, etc. We certainly don't cover *nearly* all that we
could. I did also add to that wiki page your suggestion about
meetup.com (I forgot the other site you mentioned, so didn't manage to
add that other one). Anyway, wiki page is here:
https://secure.balug.org/wiki/doku.php?id=balug:event_communications
Certainly, at least within reason, pretty much anyone can update/improve
that page and/or volunteer to assist with publicity and event
communications/announcements.
And for those that occasionally wonder exactly who the
balug-speaker-coordinators(a)balug.org alias gets forwarded to,
one can peek towards the bottom of:
http://www.wiki.balug.org/wiki/doku.php?id=balug:balug_speaker_coordination
(Yep, I even peek there rather regularly myself when I'm trying to
remember exactly who is/isn't on that alias - not the authoritative
reference, but I do accurately maintain it).