Will be doing some system maintenance, so,
some ancillary BALUG services will be intermittently unavailable.
Note that this WILL NOT IMPACT: main web site and its pages:
http://www.balug.org/
nor our mail lists or email infrastructure.
It WILL IMPACT some other services, at least intermittently,
e.g.:
http://www.archive.balug.org/http://www.wiki.balug.org/wiki
etc.
Technical details:
If it's on 208.96.15.254 it will be impacted.
The (qeum-kvm) virtual machine guest on that IP will be undergoing some
maintenance:
"convert" /usr, /var, and /home filesystems from reiserfs to ext3
(well, actually do a final rsyncs from ro mounted filesystems in
single user mode, then switch 'em out and reboot)
(and probably also continue up/cross grade from i386 to amd64)
Will be doing some system upgrades, so,
some ancillary BALUG services will be intermittently unavailable.
Note that this WILL NOT IMPACT: main web site and its pages:
http://www.balug.org/
nor our mail lists or email infrastructure.
It WILL IMPACT some other services, at least intermittently,
e.g.:
http://www.archive.balug.org/http://www.wiki.balug.org/wiki
etc.
Technical details:
If it's on 208.96.15.254 it will be impacted.
The (qeum-kvm) virtual machine guest on that IP will be getting upgraded
from: Debian GNU/Linux 6.0.9 (squeeze) i386
to: Debian GNU/Linux 7.5 (wheezy)
(and possibly also up/cross graded from i386 to amd64, or may defer
that)
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