Relocating koha.org services
Hi, all. With the shift of koha.org-related services from Metavore (LibLime's former owner) to PTFS, we're going to be relocating a few of the services that currently reside on Metavore assets. Most notably, wiki.koha.org and git.koha.org are going to move to a new system. This will involve a bit of semi-downtime for each due to DNS propagation. It's undesirable and unnecessary to lose read access to these services; I'll copy the data to the new location, redefine the DNS entries, and convergence can take its sweet time. However, in order to minimize data syncronization issues, I'm requesting that no changes be made to either of them after 2010-04-12 07:00 UTC. I'll complete the transfer sometime during the 24-hr period after that. Once DNS convergence is complete (theoretically only two hours, but waiting 12 will be safer), I'll shut down the old service locations and it will be safe to resume changes. I'll send another announcement when that window has passed. Please forward this to any relevant lists or individuals. Enjoy, Clay
On Fri, Apr 09, 2010 at 12:36:10PM -0700, Clay Fouts wrote:
Hi, all.
With the shift of koha.org-related services from Metavore (LibLime's former owner) to PTFS, we're going to be relocating a few of the services that currently reside on Metavore assets. Most notably, wiki.koha.org and git.koha.org are going to move to a new system. This will involve a bit of semi-downtime for each due to DNS propagation.
It's undesirable and unnecessary to lose read access to these services; I'll copy the data to the new location, redefine the DNS entries, and convergence can take its sweet time. However, in order to minimize data syncronization issues, I'm requesting that no changes be made to either of them after 2010-04-12 07:00 UTC. I'll complete the transfer sometime during the 24-hr period after that. Once DNS convergence is complete (theoretically only two hours, but waiting 12 will be safer), I'll shut down the old service locations and it will be safe to resume changes. I'll send another announcement when that window has passed.
Just my $0.02: In the past I had to setup various failover systems, so I usually use very low ttl (2 sec or so) in DNS entries (wiki.koha.org and git.koha.org) before migration (it seems that current ttl is 7200 seconds, so at least two hours before migration) and after switch make mod_rewrite proxy rule on old server which would proxy all requests to new one (using IP adress for obvious reasons) until everthing in DNS expires. Another alternative might be to add wiki2 and git2 aliases to new IP adress and issue 302 Location redirects on old server until DNS expires. Hopefully, this might help transitions smoother in future. -- Dobrica Pavlinusic 2share!2flame dpavlin@rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin
Thanks for the feedback. Unfortunately, because of limitations imposed by the DNS hosting service (zoneedit.com), I have no influence over the TTL value. It's stuck at 7200 seconds. The redirect for the wiki is a good idea and simple to implement, so I'll add that to the process. However, it's not possible to do this with the Git repo, AFAIK, so it would be fruitless to do so with the gitweb interface. Cheers, Clay On Sat, Apr 10, 2010 at 2:08 PM, Dobrica Pavlinusic <dpavlin@rot13.org>wrote:
Hi, all.
With the shift of koha.org-related services from Metavore (LibLime's
On Fri, Apr 09, 2010 at 12:36:10PM -0700, Clay Fouts wrote: former
owner) to PTFS, we're going to be relocating a few of the services that currently reside on Metavore assets. Most notably, wiki.koha.org and git.koha.org are going to move to a new system. This will involve a bit of semi-downtime for each due to DNS propagation.
It's undesirable and unnecessary to lose read access to these services; I'll copy the data to the new location, redefine the DNS entries, and convergence can take its sweet time. However, in order to minimize data syncronization issues, I'm requesting that no changes be made to either of them after 2010-04-12 07:00 UTC. I'll complete the transfer sometime during the 24-hr period after that. Once DNS convergence is complete (theoretically only two hours, but waiting 12 will be safer), I'll shut down the old service locations and it will be safe to resume changes. I'll send another announcement when that window has passed.
Just my $0.02:
In the past I had to setup various failover systems, so I usually use very low ttl (2 sec or so) in DNS entries (wiki.koha.org and git.koha.org) before migration (it seems that current ttl is 7200 seconds, so at least two hours before migration) and after switch make mod_rewrite proxy rule on old server which would proxy all requests to new one (using IP adress for obvious reasons) until everthing in DNS expires.
Another alternative might be to add wiki2 and git2 aliases to new IP adress and issue 302 Location redirects on old server until DNS expires.
Hopefully, this might help transitions smoother in future.
-- Dobrica Pavlinusic 2share!2flame dpavlin@rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin
I have completed (ostensibly) moving both of these services, and the DNS has had (again, ostensibly) enough time to propagate. Please feel encouraged to kick the tires and let me know if you notice any discrepancies in behavior. There should be no noticeable difference other than those two hostnames now resolve to 174.129.238.79. Thank you, Clay On Fri, Apr 9, 2010 at 12:36 PM, Clay Fouts <cfouts@ptfs.com> wrote:
Hi, all.
With the shift of koha.org-related services from Metavore (LibLime's former owner) to PTFS, we're going to be relocating a few of the services that currently reside on Metavore assets. Most notably, wiki.koha.org and git.koha.org are going to move to a new system. This will involve a bit of semi-downtime for each due to DNS propagation.
It's undesirable and unnecessary to lose read access to these services; I'll copy the data to the new location, redefine the DNS entries, and convergence can take its sweet time. However, in order to minimize data syncronization issues, I'm requesting that no changes be made to either of them after 2010-04-12 07:00 UTC. I'll complete the transfer sometime during the 24-hr period after that. Once DNS convergence is complete (theoretically only two hours, but waiting 12 will be safer), I'll shut down the old service locations and it will be safe to resume changes. I'll send another announcement when that window has passed.
Please forward this to any relevant lists or individuals.
Enjoy, Clay
2010/4/13 Clay Fouts <cfouts@ptfs.com>:
I have completed (ostensibly) moving both of these services, and the DNS has had (again, ostensibly) enough time to propagate. Please feel encouraged to kick the tires and let me know if you notice any discrepancies in behavior. There should be no noticeable difference other than those two hostnames now resolve to 174.129.238.79.
Hi Clay Thanks for that, all seems fine from here. Chris
Hi, 2010/4/12 Clay Fouts <cfouts@ptfs.com>:
I have completed (ostensibly) moving both of these services, and the DNS has had (again, ostensibly) enough time to propagate. Please feel encouraged to kick the tires and let me know if you notice any discrepancies in behavior. There should be no noticeable difference other than those two hostnames now resolve to 174.129.238.79.
I am unable to push patches to the new git.koha.org. Gitosis no longer seems to be accepting my public key - can you double-check and confirm that the Gitosis setup survived the move? $ git push gitosis@git.koha.org:koha.git master:master Permission denied (publickey). fatal: The remote end hung up unexpectedly Regards, Galen -- Galen Charlton gmcharlt@gmail.com
On 13 April 2010 13:11, Galen Charlton <gmcharlt@gmail.com> wrote:
Hi,
2010/4/12 Clay Fouts <cfouts@ptfs.com>:
I have completed (ostensibly) moving both of these services, and the DNS has had (again, ostensibly) enough time to propagate. Please feel encouraged to kick the tires and let me know if you notice any discrepancies in behavior. There should be no noticeable difference other than those two hostnames now resolve to 174.129.238.79.
I am unable to push patches to the new git.koha.org. Gitosis no longer seems to be accepting my public key - can you double-check and confirm that the Gitosis setup survived the move?
$ git push gitosis@git.koha.org:koha.git master:master Permission denied (publickey). fatal: The remote end hung up unexpectedly
Ooops yeah spoke to soon <aol> me too </aol> The authenticity of host 'git.koha.org (174.129.238.79)' can't be established. RSA key fingerprint is 68:0b:bc:8a:e9:84:36:67:7a:61:d8:c9:62:06:31:80. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'git.koha.org,174.129.238.79' (RSA) to the list of known hosts. Enter passphrase for key '/home/chris/.ssh/identity': Permission denied (publickey). fatal: The remote end hung up unexpectedly Chris
Gitosis was missing completely, actually. I've installed and re-mapped the configuration. Test it again now, please. Thanks, Clay On Mon, Apr 12, 2010 at 6:11 PM, Galen Charlton <gmcharlt@gmail.com> wrote:
Hi,
2010/4/12 Clay Fouts <cfouts@ptfs.com>:
I have completed (ostensibly) moving both of these services, and the DNS has had (again, ostensibly) enough time to propagate. Please feel encouraged to kick the tires and let me know if you notice any discrepancies in behavior. There should be no noticeable difference other than those two hostnames now resolve to 174.129.238.79.
I am unable to push patches to the new git.koha.org. Gitosis no longer seems to be accepting my public key - can you double-check and confirm that the Gitosis setup survived the move?
$ git push gitosis@git.koha.org:koha.git master:master Permission denied (publickey). fatal: The remote end hung up unexpectedly
Regards,
Galen -- Galen Charlton gmcharlt@gmail.com
Hi, On Tue, Apr 13, 2010 at 3:02 AM, Clay Fouts <cfouts@ptfs.com> wrote:
Gitosis was missing completely, actually. I've installed and re-mapped the configuration. Test it again now, please.
Closer, but no dice yet: $ git push gitosis@git.koha.org:koha.git master:master Counting objects: 19, done. Delta compression using up to 4 threads. Compressing objects: 100% (8/8), done. Writing objects: 100% (10/10), 904 bytes, done. Total 10 (delta 6), reused 0 (delta 0) error: unable to create temporary sha1 filename ./objects/47: File exists fatal: failed to write object error: unpack failed: unpacker exited with error code To gitosis@git.koha.org:koha.git ! [remote rejected] master -> master (n/a (unpacker error)) error: failed to push some refs to 'gitosis@git.koha.org:koha.git' This error message usually indicates a file permissions problem. Regards, Galen -- Galen Charlton gmcharlt@gmail.com
Hooray for progress. How about now? Clay On Tue, Apr 13, 2010 at 4:25 AM, Galen Charlton <gmcharlt@gmail.com> wrote:
Hi,
Gitosis was missing completely, actually. I've installed and re-mapped
On Tue, Apr 13, 2010 at 3:02 AM, Clay Fouts <cfouts@ptfs.com> wrote: the
configuration. Test it again now, please.
Closer, but no dice yet:
$ git push gitosis@git.koha.org:koha.git master:master Counting objects: 19, done. Delta compression using up to 4 threads. Compressing objects: 100% (8/8), done. Writing objects: 100% (10/10), 904 bytes, done. Total 10 (delta 6), reused 0 (delta 0) error: unable to create temporary sha1 filename ./objects/47: File exists
fatal: failed to write object error: unpack failed: unpacker exited with error code To gitosis@git.koha.org:koha.git ! [remote rejected] master -> master (n/a (unpacker error)) error: failed to push some refs to 'gitosis@git.koha.org:koha.git'
This error message usually indicates a file permissions problem.
Regards,
Galen -- Galen Charlton gmcharlt@gmail.com
participants (4)
-
Chris Cormack -
Clay Fouts -
Dobrica Pavlinusic -
Galen Charlton