Re: [Zope-dev] Re: svn.zope.org borked
Jens Vagelpohl wrote: On 21 Dec 2005, at 16:15, Jens Vagelpohl wrote: With this upgrade in place I will do a new dry-run for the FSFS backend migration tomorrow morning. The test run ran through without any problems. Here's some stats: - dumping the existing repository took 12 minutes and resulted in a 1.1 GB file - loading the file into a new fsfs-based repo took 31 minutes. The resulting repository is 662 MB in size. As Tim predicted, this is smaller then the BDB-based repo, which is 711 MB now. Jim, if you want to take a look at this new repository, it's under / root/fakesvn. I moved this to the normal repos area and changed the group to the zopesvn, so that everyone with access to the old repository should have access to this one. The repository is named test, so so it is accesible at svn+ssh://svn.zope.org/repos/test/Zope3/trunk and svn://svn.zope.org/repos/test/Zope3/trunk. I encourage people to check it out. One thing I noticed is that I can't commit any changes. I imagine that the group needs write access to some directory or files that it doesn't have write access to now. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 23 Dec 2005, at 14:48, Jim Fulton wrote: Jim, if you want to take a look at this new repository, it's under / root/fakesvn. I moved this to the normal repos area and changed the group to the zopesvn, so that everyone with access to the old repository should have access to this one. The repository is named test, so so it is accesible at svn+ssh://svn.zope.org/repos/test/Zope3/trunk and svn://svn.zope.org/repos/test/Zope3/trunk. I encourage people to check it out. One thing I noticed is that I can't commit any changes. I imagine that the group needs write access to some directory or files that it doesn't have write access to now. Yes, one item on the action plan for the migration is to ensure the ownerships and access settings are duplicated exactly as they are on the current repository. This has to be done manually after the migration. I didnn't do it on this test migration because I did not know you were going to make it publicly available ;) jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 23 Dec 2005, at 14:57, Jens Vagelpohl wrote: On 23 Dec 2005, at 14:48, Jim Fulton wrote: Jim, if you want to take a look at this new repository, it's under / root/fakesvn. I moved this to the normal repos area and changed the group to the zopesvn, so that everyone with access to the old repository should have access to this one. The repository is named test, so so it is accesible at svn+ssh://svn.zope.org/repos/test/Zope3/trunk and svn://svn.zope.org/repos/test/Zope3/trunk. I encourage people to check it out. One thing I noticed is that I can't commit any changes. I imagine that the group needs write access to some directory or files that it doesn't have write access to now. I fixed the permissions and just did a test checkin to verify it works now. jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
Jens Vagelpohl wrote: On 23 Dec 2005, at 14:57, Jens Vagelpohl wrote: On 23 Dec 2005, at 14:48, Jim Fulton wrote: Jim, if you want to take a look at this new repository, it's under / root/fakesvn. I moved this to the normal repos area and changed the group to the zopesvn, so that everyone with access to the old repository should have access to this one. The repository is named test, so so it is accesible at svn+ssh://svn.zope.org/repos/test/Zope3/trunk and svn://svn.zope.org/repos/test/Zope3/trunk. I encourage people to check it out. One thing I noticed is that I can't commit any changes. I imagine that the group needs write access to some directory or files that it doesn't have write access to now. I fixed the permissions and just did a test checkin to verify it works now. Cool. Works for me too. I encourage people to play with it. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 21 Dec 2005, at 16:15, Jens Vagelpohl wrote: With this upgrade in place I will do a new dry-run for the FSFS backend migration tomorrow morning. The test run ran through without any problems. Here's some stats: - dumping the existing repository took 12 minutes and resulted in a 1.1 GB file - loading the file into a new fsfs-based repo took 31 minutes. The resulting repository is 662 MB in size. As Tim predicted, this is smaller then the BDB-based repo, which is 711 MB now. Jim, if you want to take a look at this new repository, it's under / root/fakesvn. Barring any complaints I'll go ahead with the conversion this coming Sunday, December 25th. jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
I'm going to go ahead with this update in hopes of resolving some windows client problems that may be confounding our efforts to run windows tests with buildbot. Jim Jens Vagelpohl wrote: On 19 Dec 2005, at 22:08, Jim Fulton wrote: Sounds good. I'll announce that the repo will be down for maintenance on the 25th, Just FYI, during a dry run this morning I hit an obvious snag: The subversion packages on svn.zope.org are so ancient that they cannot create FSFS backends. What I was able to test so far is dumping: It takes just 10 minutes and creates a file 1.1GB in size, so that's good. I had a look at the packages on the box and luckily the (rather obscure) source they are from does supply newer ones: http://summersoft.fay.ar.us/pub/subversion/latest/redhat-9.0/bin/ From eyeballing the RPM requirements and then doing a dry-run the packages that will need updating are... - swig (1.3.19-1.1 to 1.3.19-3) - subversion (1.0.6-1 to 1.2.3-1) - subversion-tools (1.0.6-1 to 1.2.3-1) - subversion-python (1.0.6-1 to 1.2.3-1) This additional packages needs to be installed for svn-tools: - subversion-perl (1.2.3-1) Since I cannot do any test right now for loading the dumpfile into a FSFS-based repository I suggest doing this package upgrade beforehand. It only takes a few minutes. I cannot make any guarantees that nothing will break, however. The only major upgrade to a running SVN setup that I have done was 1.1 to 1.2.1 and that was perfectly fine. How should I proceed? jens -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
Does that mean you're doing it? All necessary RPMs are on the box at / root/svnupgrade/. Otherwise I can do it tomorrow morning (about 5 AM EST) jens On 21 Dec 2005, at 16:08, Jim Fulton wrote: I'm going to go ahead with this update in hopes of resolving some windows client problems that may be confounding our efforts to run windows tests with buildbot. Jim Jens Vagelpohl wrote: On 19 Dec 2005, at 22:08, Jim Fulton wrote: Sounds good. I'll announce that the repo will be down for maintenance on the 25th, Just FYI, during a dry run this morning I hit an obvious snag: The subversion packages on svn.zope.org are so ancient that they cannot create FSFS backends. What I was able to test so far is dumping: It takes just 10 minutes and creates a file 1.1GB in size, so that's good. I had a look at the packages on the box and luckily the (rather obscure) source they are from does supply newer ones: http://summersoft.fay.ar.us/pub/subversion/latest/redhat-9.0/bin/ From eyeballing the RPM requirements and then doing a dry-run the packages that will need updating are... - swig (1.3.19-1.1 to 1.3.19-3) - subversion (1.0.6-1 to 1.2.3-1) - subversion-tools (1.0.6-1 to 1.2.3-1) - subversion-python (1.0.6-1 to 1.2.3-1) This additional packages needs to be installed for svn-tools: - subversion-perl (1.2.3-1) Since I cannot do any test right now for loading the dumpfile into a FSFS-based repository I suggest doing this package upgrade beforehand. It only takes a few minutes. I cannot make any guarantees that nothing will break, however. The only major upgrade to a running SVN setup that I have done was 1.1 to 1.2.1 and that was perfectly fine. How should I proceed? jens -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
Jim Fulton wrote: I'm going to go ahead with this update in hopes of resolving some windows client problems that may be confounding our efforts to run windows tests with buildbot. Done Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
Jens Vagelpohl wrote: Does that mean you're doing it? All necessary RPMs are on the box at / root/svnupgrade/. Otherwise I can do it tomorrow morning (about 5 AM EST) Yes, already done. They are also available in my home directory. :) Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 21 Dec 2005, at 16:12, Jim Fulton wrote: Jim Fulton wrote: I'm going to go ahead with this update in hopes of resolving some windows client problems that may be confounding our efforts to run windows tests with buildbot. Done Great. I can see http://svn.zope.org works just fine. With this upgrade in place I will do a new dry-run for the FSFS backend migration tomorrow morning. jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 19 Dec 2005, at 22:08, Jim Fulton wrote: Sounds good. I'll announce that the repo will be down for maintenance on the 25th, Just FYI, during a dry run this morning I hit an obvious snag: The subversion packages on svn.zope.org are so ancient that they cannot create FSFS backends. What I was able to test so far is dumping: It takes just 10 minutes and creates a file 1.1GB in size, so that's good. I had a look at the packages on the box and luckily the (rather obscure) source they are from does supply newer ones: http://summersoft.fay.ar.us/pub/subversion/latest/redhat-9.0/bin/ From eyeballing the RPM requirements and then doing a dry-run the packages that will need updating are... - swig (1.3.19-1.1 to 1.3.19-3) - subversion (1.0.6-1 to 1.2.3-1) - subversion-tools (1.0.6-1 to 1.2.3-1) - subversion-python (1.0.6-1 to 1.2.3-1) This additional packages needs to be installed for svn-tools: - subversion-perl (1.2.3-1) Since I cannot do any test right now for loading the dumpfile into a FSFS-based repository I suggest doing this package upgrade beforehand. It only takes a few minutes. I cannot make any guarantees that nothing will break, however. The only major upgrade to a running SVN setup that I have done was 1.1 to 1.2.1 and that was perfectly fine. How should I proceed? jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
Jens Vagelpohl wrote: On 19 Dec 2005, at 22:08, Jim Fulton wrote: Sounds good. I'll announce that the repo will be down for maintenance on the 25th, Just FYI, during a dry run this morning I hit an obvious snag: The subversion packages on svn.zope.org are so ancient that they cannot create FSFS backends. What I was able to test so far is dumping: It takes just 10 minutes and creates a file 1.1GB in size, so that's good. I had a look at the packages on the box and luckily the (rather obscure) source they are from does supply newer ones: http://summersoft.fay.ar.us/pub/subversion/latest/redhat-9.0/bin/ From eyeballing the RPM requirements and then doing a dry-run the packages that will need updating are... - swig (1.3.19-1.1 to 1.3.19-3) - subversion (1.0.6-1 to 1.2.3-1) - subversion-tools (1.0.6-1 to 1.2.3-1) - subversion-python (1.0.6-1 to 1.2.3-1) This additional packages needs to be installed for svn-tools: - subversion-perl (1.2.3-1) Since I cannot do any test right now for loading the dumpfile into a FSFS-based repository I suggest doing this package upgrade beforehand. It only takes a few minutes. I cannot make any guarantees that nothing will break, however. The only major upgrade to a running SVN setup that I have done was 1.1 to 1.2.1 and that was perfectly fine. How should I proceed? Go for it. But please, just to be safe, let's wait until the next round of betas is out. Hopefully, this will happen in the next couple of days. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 20 Dec 2005, at 11:57, Jim Fulton wrote: Since I cannot do any test right now for loading the dumpfile into a FSFS-based repository I suggest doing this package upgrade beforehand. It only takes a few minutes. I cannot make any guarantees that nothing will break, however. The only major upgrade to a running SVN setup that I have done was 1.1 to 1.2.1 and that was perfectly fine. How should I proceed? Go for it. But please, just to be safe, let's wait until the next round of betas is out. Hopefully, this will happen in the next couple of days. OK, I'll watch the situation. I have everything in place on the box for the upgrade. If all else fails I could always do the upgrade and a dump/load test on 12/25 and only proceed if it succeeds. jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jens, I have the latest subversion-1.2.3-4 compiled for python2.3. I am happy to make them available to you if you wish. Alan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDp/1gCfroLk4EZpkRAg9jAKCAUkIuyhK1q7mrCiscfxpSM7tMwACeLt3J WIn0K8ovArTGMtcKnO+MOCw= =oFtk -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 20 Dec 2005, at 12:47, Alan Milligan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jens, I have the latest subversion-1.2.3-4 compiled for python2.3. I am happy to make them available to you if you wish. Thanks for the help, Alan. I'm just going the route of least risk by using the same set of matching packages from that packager first - if there are problems I'll take you up on your offer ;) jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
Rocky Burt wrote: Perhaps the backend should be switched from bdb to fsfs (native subversion backend type) ? I know it does away with a lot of these, issues. Yup, when someone has time to do it. AFAIK, it will involve dumping the repository and reloading it. Past experience suggests that this will take several hours. This involves scheduled downtime, testing, dealing with the inevitable misshap I expect the Zope Foundation will probably establish a new repository. That would probably be a good time to make the switch. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 19 Dec 2005, at 20:02, Jim Fulton wrote: Rocky Burt wrote: Perhaps the backend should be switched from bdb to fsfs (native subversion backend type) ? I know it does away with a lot of these, issues. Yup, when someone has time to do it. AFAIK, it will involve dumping the repository and reloading it. Past experience suggests that this will take several hours. This involves scheduled downtime, testing, dealing with the inevitable misshap IMHO the process is straightforward and easy (except for the time it will take), and there is no problem reverting to the previous state: - run svnadmin dump on the old repository - move the old repository aside - create a new repository with fsfs backend - run svnadmin load to load the data into the new repository At no point would any data be in danger. The problem I see on the current box is hard drive space. I'm not sure the remaining space is enough to hold a complete dump *and* the new repository along with the old one. jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
Jens Vagelpohl wrote: On 19 Dec 2005, at 20:02, Jim Fulton wrote: Rocky Burt wrote: Perhaps the backend should be switched from bdb to fsfs (native subversion backend type) ? I know it does away with a lot of these, issues. Yup, when someone has time to do it. AFAIK, it will involve dumping the repository and reloading it. Past experience suggests that this will take several hours. This involves scheduled downtime, testing, dealing with the inevitable misshap IMHO the process is straightforward and easy (except for the time it will take), That fact alone adds complication, as that down time needs to be scheduled. and there is no problem reverting to the previous state: - run svnadmin dump on the old repository - move the old repository aside - create a new repository with fsfs backend - run svnadmin load to load the data into the new repository I presume you also need to disable access to the repository while this is going on. That means there are three input paths (viewcvs, svn:, svn+ssh:) that need to be disabled. Maybe that's just a matter of renaming the repo. At no point would any data be in danger. The problem I see on the current box is hard drive space. I'm not sure the remaining space is enough to hold a complete dump *and* the new repository along with the old one. The whole repository is only about 800 megs. There are over 8 gigs free. Are the dump file or the file-based repo much larger in size the the Berkeley database? BTW, thanks for volunteering for this! It will be great not to fool with the Berkeley DB anymore. :) Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 19 Dec 2005, at 21:27, Jim Fulton wrote: IMHO the process is straightforward and easy (except for the time it will take), That fact alone adds complication, as that down time needs to be scheduled. OK, well, the only complication is setting a date really. Someone decides and publishes it on the different lists, end of story. and there is no problem reverting to the previous state: - run svnadmin dump on the old repository - move the old repository aside - create a new repository with fsfs backend - run svnadmin load to load the data into the new repository I presume you also need to disable access to the repository while this is going on. That means there are three input paths (viewcvs, svn:, svn+ssh:) that need to be disabled. Maybe that's just a matter of renaming the repo. viewcvs is disabled by either shutting down Apache or putting up some meaningful error page. svn access is disabled by editing /etc/ xinetd.d/svn and restarting xinetd. svn+ssh can be disabled by editing /etc/ssh/sshd_config to restrict access. This is a matter of minutes, really. At no point would any data be in danger. The problem I see on the current box is hard drive space. I'm not sure the remaining space is enough to hold a complete dump *and* the new repository along with the old one. The whole repository is only about 800 megs. There are over 8 gigs free. Are the dump file or the file-based repo much larger in size the the Berkeley database? I'm not sure, really, but knowing the current size (which I had not checked) makes me confident we're fine on that front. BTW, thanks for volunteering for this! It will be great not to fool with the Berkeley DB anymore. :) Umh, more like force-volunteered now ;) Which is fine, but in return I'd like someone else (maybe you?) to herd the cats and come up with a time frame where this can be done, and communicating it. I'll do everything on the technical side. Sound like a deal? jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 19 Dec 2005, at 21:37, Jens Vagelpohl wrote: BTW, thanks for volunteering for this! It will be great not to fool with the Berkeley DB anymore. :) Umh, more like force-volunteered now ;) Which is fine, but in return I'd like someone else (maybe you?) to herd the cats and come up with a time frame where this can be done, and communicating it. I'll do everything on the technical side. Sound like a deal? P.S.: The best time for me is between 12/25 and 12/30 since I'll be at home in Germany. jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
Jens Vagelpohl wrote: On 19 Dec 2005, at 21:27, Jim Fulton wrote: IMHO the process is straightforward and easy (except for the time it will take), That fact alone adds complication, as that down time needs to be scheduled. OK, well, the only complication is setting a date really. Someone decides and publishes it on the different lists, end of story. and there is no problem reverting to the previous state: - run svnadmin dump on the old repository - move the old repository aside - create a new repository with fsfs backend - run svnadmin load to load the data into the new repository I presume you also need to disable access to the repository while this is going on. That means there are three input paths (viewcvs, svn:, svn+ssh:) that need to be disabled. Maybe that's just a matter of renaming the repo. viewcvs is disabled by either shutting down Apache It's also used for CVS. (Maybe mailman too?) or putting up some meaningful error page. Which has to be written. svn access is disabled by editing /etc/ xinetd.d/svn and restarting xinetd. Uh huh. svn+ssh can be disabled by editing /etc/ssh/sshd_config to restrict access. This is a matter of minutes, really. I didn't think you could use sshd_config to restrict use of a single program. ssh access is still needed for CVS and for people logging in to do other work (e.g. mailman admin). Moving the repo seems a lot easier. :) At no point would any data be in danger. The problem I see on the current box is hard drive space. I'm not sure the remaining space is enough to hold a complete dump *and* the new repository along with the old one. The whole repository is only about 800 megs. There are over 8 gigs free. Are the dump file or the file-based repo much larger in size the the Berkeley database? I'm not sure, really, but knowing the current size (which I had not checked) makes me confident we're fine on that front. Of course, you'll want to do a dry run to make sure. BTW, thanks for volunteering for this! It will be great not to fool with the Berkeley DB anymore. :) Umh, more like force-volunteered now ;) :) Which is fine, but in return I'd like someone else (maybe you?) to herd the cats and come up with a time frame where this can be done, and communicating it. I'll do everything on the technical side. Sound like a deal? Sure. Thanks again. :) Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
Jens Vagelpohl wrote: On 19 Dec 2005, at 21:37, Jens Vagelpohl wrote: BTW, thanks for volunteering for this! It will be great not to fool with the Berkeley DB anymore. :) Umh, more like force-volunteered now ;) Which is fine, but in return I'd like someone else (maybe you?) to herd the cats and come up with a time frame where this can be done, and communicating it. I'll do everything on the technical side. Sound like a deal? P.S.: The best time for me is between 12/25 and 12/30 since I'll be at home in Germany. Pick a date and I'll propose it. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 19 Dec 2005, at 21:44, Jim Fulton wrote: Umh, more like force-volunteered now ;) Which is fine, but in return I'd like someone else (maybe you?) to herd the cats and come up with a time frame where this can be done, and communicating it. I'll do everything on the technical side. Sound like a deal? P.S.: The best time for me is between 12/25 and 12/30 since I'll be at home in Germany. Pick a date and I'll propose it. Since traffic will probably be low and I'll definitely be around Sunday 12/25 would be my choice. I'd probably be starting on it at noon (6 AM EST). Testing disk space usage by running a full dump and load can be done at any time. The dump can be done on the live repository without ill effect and the loading can be done somewhere else on the file system, again with no side effects (apart from slowing down the machine due to disk access). I can kick that off any day this week in the morning, any preference? jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
[Jim] ... The whole repository is only about 800 megs. There are over 8 gigs free. Are the dump file or the file-based repo much larger in size the the Berkeley database? FYI, if you don't want to read the code ;-), the book says an FSFS repository is slightly smaller than the same thing under BDB: http://svnbook.red-bean.com/en/1.1/ch05.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
Jens Vagelpohl wrote: On 19 Dec 2005, at 21:44, Jim Fulton wrote: Umh, more like force-volunteered now ;) Which is fine, but in return I'd like someone else (maybe you?) to herd the cats and come up with a time frame where this can be done, and communicating it. I'll do everything on the technical side. Sound like a deal? P.S.: The best time for me is between 12/25 and 12/30 since I'll be at home in Germany. Pick a date and I'll propose it. Since traffic will probably be low and I'll definitely be around Sunday 12/25 would be my choice. I'd probably be starting on it at noon (6 AM EST). Testing disk space usage by running a full dump and load can be done at any time. The dump can be done on the live repository without ill effect and the loading can be done somewhere else on the file system, again with no side effects (apart from slowing down the machine due to disk access). I can kick that off any day this week in the morning, any preference? Sounds good. I'll announce that the repo will be down for maintenance on the 25th, Thanks again! Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: svn.zope.org borked
On 19 Dec 2005, at 22:08, Tim Peters wrote: [Jim] ... The whole repository is only about 800 megs. There are over 8 gigs free. Are the dump file or the file-based repo much larger in size the the Berkeley database? FYI, if you don't want to read the code ;-), the book says an FSFS repository is slightly smaller than the same thing under BDB: http://svnbook.red-bean.com/en/1.1/ch05.html Sounds good. Now as long as the dump file isn't over 6 GB in size we should be OK ;) jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
