27 Jan
2016
27 Jan
'16
5:13 a.m.
All,
As some of you may be already aware, this past December I was notified
our current virtual server that hosts a broad array of outreach
services, including these mailing lists, will be decommissioned at the
end of this month. Since, I've been working on securing the
infrastructure and ongoing support onto a brand new physical blade. I am
pleased to report we are at the very end of what has proven to be a
fairly intense journey (needless to mention I learned a lot more than I
ever wanted to about sysadmin). Our new setup is considerably more
powerful and I am confident it will offer a significant improvement in
performance over the old one. As we enter the final stage in the porting
process, there will be a brief downtime tentatively scheduled for 11am
Eastern Time (East US Coast) tomorrow, Wednesday, January 27th. During
this time, you will experience inability to access hosted services,
including web and mailing lists. My intent is to have the transition
complete as quickly as we can do the final rsync and IP address
reconfiguration. I will let you know as soon as we've completed this
final step. Thank you for your support and understanding.
Best,
--
Ivica Ico Bukvic, D.M.A.
Associate Professor
Creative Technologies in Music
ICAT Senior Fellow
Director -- DISIS, L2Ork
Virginia Tech
School of Performing Arts – 0141
Blacksburg, VA 24061
(540) 231-6139
www.performingarts.vt.edu
disis.music.vt.edu
l2ork.music.vt.edu
ico.bukvic.net
27 Jan
27 Jan
7:30 a.m.
On 01/27/16 05:12, Ivica Ico Bukvic wrote:
I am pleased to report we are at the very end of what
has proven to be a
fairly intense journey (needless to mention I learned a lot more than I
ever wanted to about sysadmin).
...
As we enter the final stage in the porting
process, there will be a brief downtime tentatively scheduled for 11am
Eastern Time (East US Coast) tomorrow, Wednesday, January 27th.
Hi Ico
I thought I would share a hint on server migration wrt dns configurations.
The dns configuration has a ttl field. This field signifies to the
clients how long the ip address they get when they do the lookup is
valid, ie. the time that must at-most pass before they ask the dns
server again.
When changing the ip address in a dns configuration all the clients who
already have a valid token will keep on using this token (with the old
ip address) until their respective ttl's have expired.
This is what I usually do to solve this problem:
Lets assume the current ttl is set to 86400 (24h).
24 hours before I plan to do the migration I set the ttl to 3600 (1h).
Then 1 hour before the migration I change it again, this time to 600 (10m).
And finally 10 minutes before the migration I change it to 0.
At the time of migration I now know that all clients are asking the dns
server for ip all the time and nobody will get the wrong (old) ip
address once I have changed it.
When the new ip address has been set in the configuration the ttl can
now be changed back to 86400.
The amount of "steps" to use (24h, 1h, 1m, ...) highly depends on the
amount of dns lookups on the dns server since setting the ttl to 0 24h
before migration might result in a serious extra dns server load.
Good luck with the final migration :-)
Kind regards
Bent Bisballe Nyeng
12:01 p.m.
Hi Bent,
24 hours before I plan to do the migration I set the
ttl to 3600 (1h).
Then 1 hour before the migration I change it again, this time to 600 (10m).
And finally 10 minutes before the migration I change it to 0.
Thanks for the tips! In this case it seems we are going to switch the IP
from server to server rather than change DNS.
Cheers!
Daniel
7:18 p.m.
All,
The migration should be now complete. Please let us know if you
encounter any problems.
Best,
Ico
On 1/26/2016 11:12 PM, Ivica Ico Bukvic wrote:
All,
As some of you may be already aware, this past December I was notified
our current virtual server that hosts a broad array of outreach
services, including these mailing lists, will be decommissioned at the
end of this month. Since, I've been working on securing the
infrastructure and ongoing support onto a brand new physical blade. I
am pleased to report we are at the very end of what has proven to be a
fairly intense journey (needless to mention I learned a lot more than
I ever wanted to about sysadmin). Our new setup is considerably more
powerful and I am confident it will offer a significant improvement in
performance over the old one. As we enter the final stage in the
porting process, there will be a brief downtime tentatively scheduled
for 11am Eastern Time (East US Coast) tomorrow, Wednesday, January
27th. During this time, you will experience inability to access hosted
services, including web and mailing lists. My intent is to have the
transition complete as quickly as we can do the final rsync and IP
address reconfiguration. I will let you know as soon as we've
completed this final step. Thank you for your support and understanding.
Best,
3005
days inactive
3005
days old
consortium@lists.linuxaudio.org
3 comments
3 participants
participants (3)
-
Bent Bisballe Nyeng -
Daniel James -
Ivica Ico Bukvic