Dear all,
the op25.osmocom.org site is currently a lxc (linxu container) setup on one of my servers, and it frequently locks up the entire container every so often, without any reason why. I have failed to find the root cause of this and given up by now.
As all of the other osmocom projects have meanwhile migrated away from trac to the redmine based setup at http://projects.osmocom.org/, I would stongly suggest the OP25 project to migrate there, too. This would include:
* migration of the wiki pages (Holger has some semi-automatic process for that which imports the content but still requires manual fix-up of a lot of formatting)
* migration of the tickets (Holger also did that programmatically for the other projects)
* import of the SVN repository to our git server (see http://git.osmocom.org)
Is there a way we can encourage the current active OP25 community to go ahead with the above migration? In the end, the closer you align in terms of infrastructure with the other osmocom.org projects, the more likely it is that the content will be available, systems and software updated, content backed up, etc. I think in the end, it would be better for everyone - including me for being responsible that the site is currently down very often.
Regards, Harald
Hi Harald
I've been talking offline with Matt about this and I think the migration to the new server is a great idea - the new infrastructure is much more reliable - but I've not been contributing here for a while. I would ask for Max's opinion as he's done the most and is the one driving things right now.
ATB
Steve
yes, Harald, and thanks for hosting OP25 and for offering to continue! 100% in favor of this and please be sure to let us know what we can do / how we can help. As for the code in SVN it would be good to migrate this - we did switch over the current code to git a while ago, and the code remaining in SVN has some legacy modules in it, so perhaps we could create a new branch in the git repo to stash this old code (stuff that we'd hope to carry forward someday).
Best Max
On Monday, April 4, 2016 5:33 AM, "Harald Welte laforge@gnumonks.org [op25-dev]" op25-dev@yahoogroups.com wrote:
Dear all,
the op25.osmocom.org site is currently a lxc (linxu container) setup on one of my servers, and it frequently locks up the entire container every so often, without any reason why. I have failed to find the root cause of this and given up by now.
As all of the other osmocom projects have meanwhile migrated away from trac to the redmine based setup at http://projects.osmocom.org/, I would stongly suggest the OP25 project to migrate there, too. This would include:
* migration of the wiki pages (Holger has some semi-automatic process for that which imports the content but still requires manual fix-up of a lot of formatting)
* migration of the tickets (Holger also did that programmatically for the other projects)
* import of the SVN repository to our git server (see http://git.osmocom.org)
Is there a way we can encourage the current active OP25 community to go ahead with the above migration? In the end, the closer you align in terms of infrastructure with the other osmocom.org projects, the more likely it is that the content will be available, systems and software updated, content backed up, etc. I think in the end, it would be better for everyone - including me for being responsible that the site is currently down very often.
Regards, Harald
On Mon, Apr 04, 2016 at 02:45:23PM +0000, ikjtel wrote:
yes, Harald, and thanks for hosting OP25 and for offering to continue! 100% in favor of this and please be sure to let us know what we can do / how we can help. As for the code in SVN it would be good to migrate this - we did switch over the current code to git a while ago, and the code remaining in SVN has some legacy modules in it, so perhaps we could create a new branch in the git repo to stash this old code (stuff that we'd hope to carry forward someday).
sure, this sounds like a great idea. It might also make sense to do a full svn->git conversion of the current repository and keep it as an 'op25-historic' git repo around. This way the full history will be preserved.
In terms of the wiki and issue migration: I'd hope that Holger could provide some insight into that.
Aside from the trac instance, are you currently running anything else on the op25.osmocom.org VM that would need to be migrated?
Regards, Harald
Hopefully Stevie can comment on this as well, but IIRC there are three services we currently depend upon op25.osmocom.org for- - wiki content (trac) - git repo (current code) - svn repo (older code)
On Monday, April 4, 2016 12:15 PM, Harald Welte laforge@gnumonks.org wrote:
On Mon, Apr 04, 2016 at 02:45:23PM +0000, ikjtel wrote:
yes, Harald, and thanks for hosting OP25 and for offering to continue! 100% in favor of this and please be sure to let us know what we can do / how we can help. As for the code in SVN it would be good to migrate this - we did switch over the current code to git a while ago, and the code remaining in SVN has some legacy modules in it, so perhaps we could create a new branch in the git repo to stash this old code (stuff that we'd hope to carry forward someday).
sure, this sounds like a great idea. It might also make sense to do a full svn->git conversion of the current repository and keep it as an 'op25-historic' git repo around. This way the full history will be preserved.
In terms of the wiki and issue migration: I'd hope that Holger could provide some insight into that.
Aside from the trac instance, are you currently running anything else on the op25.osmocom.org VM that would need to be migrated?
Regards, Harald
Hi All,
I'm sure that's it - just the trac wiki, SVN and Git repos.
Thanks for the help and the offer of continuing to host!
Cheers, Matt
On 5 April 2016 at 03:22, ikjtel ikj1234i@yahoo.com [op25-dev] < op25-dev@yahoogroups.com> wrote:
Hopefully Stevie can comment on this as well, but IIRC there are three services we currently depend upon op25.osmocom.org for-
- wiki content (trac)
- git repo (current code)
- svn repo (older code)
On Monday, April 4, 2016 12:15 PM, Harald Welte laforge@gnumonks.org wrote:
On Mon, Apr 04, 2016 at 02:45:23PM +0000, ikjtel wrote:
yes, Harald, and thanks for hosting OP25 and for offering to continue! 100% in favor of this and please be sure to let us know what we can do / how we can help. As for the code in SVN it would be good to migrate this - we did switch over the current code to git a while ago, and the code remaining in SVN has some legacy modules in it, so perhaps we could create a new branch in the git repo to stash this old code (stuff that we'd hope to carry forward someday).
sure, this sounds like a great idea. It might also make sense to do a full svn->git conversion of the current repository and keep it as an 'op25-historic' git repo around. This way the full history will be preserved.
In terms of the wiki and issue migration: I'd hope that Holger could provide some insight into that.
Aside from the trac instance, are you currently running anything else on the op25.osmocom.org VM that would need to be migrated?
Regards, Harald
--
- Harald Welte laforge@gnumonks.org
============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
Hi Max and other OP25 developers,
now that there seems to be only positive feedback so far, let's get started.
On Mon, Apr 04, 2016 at 05:22:45PM +0000, ikjtel ikj1234i@yahoo.com [op25-dev] wrote:
- wiki content (trac)
- tickets (trac
I would like to ask Holger to help here, or to help us by describing the tools used for the migration of openbsc etc. from trac to redmine.
- git repo (current code)
I think we simply push its content to git.osmocom.org at the time of the actual switch-over.
What I would need before that is a list of ssh public keys of everyone with push/commit access to the current repo, so I can import them for the new repo. Please provide me with that.
- svn repo (older code)
I will take care of importing all of that into a separte (op25-legacy?) git repository on git.osmocom.org meanwhile, to preserve the legacy.
Yeah, those are the only services we need. I am delighted that we're finally making the move :)
On 5 April 2016 at 03:22, ikjtel ikj1234i@yahoo.com [op25-dev] < op25-dev@yahoogroups.com> wrote:
Hopefully Stevie can comment on this as well, but IIRC there are three services we currently depend upon op25.osmocom.org for-
- wiki content (trac)
- git repo (current code)
- svn repo (older code)
On Monday, April 4, 2016 12:15 PM, Harald Welte laforge@gnumonks.org wrote:
On Mon, Apr 04, 2016 at 02:45:23PM +0000, ikjtel wrote:
yes, Harald, and thanks for hosting OP25 and for offering to continue! 100% in favor of this and please be sure to let us know what we can do / how we can help. As for the code in SVN it would be good to migrate this - we did switch over the current code to git a while ago, and the code remaining in SVN has some legacy modules in it, so perhaps we could create a new branch in the git repo to stash this old code (stuff that we'd hope to carry forward someday).
sure, this sounds like a great idea. It might also make sense to do a full svn->git conversion of the current repository and keep it as an 'op25-historic' git repo around. This way the full history will be preserved.
In terms of the wiki and issue migration: I'd hope that Holger could provide some insight into that.
Aside from the trac instance, are you currently running anything else on the op25.osmocom.org VM that would need to be migrated?
Regards, Harald
--
- Harald Welte laforge@gnumonks.org
============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
Dear OP25 developers,
On Thu, Apr 07, 2016 at 10:14:41AM +1000, Steve Glass wrote:
Yeah, those are the only services we need. I am delighted that we're finally making the move :)
I'm sorry that I dropped the ball on Holger for migration of the trac to redmine back in April/May 2016 :/
I've just resurrected the op25 container one more time, and installed a cron-job that restarts the container once every night (1am GMT), to make sure the content is reachable without any manual intervention by me.
Back last year, the op25-legacy svn had been converted and imported to git.osmocom.org (see http://git.osmocom.org/op25-legacy/). Also, the op25 git repo had been imported at http://git.osmocom.org/op25/
Also back then, I added your ssh public keys (Max, 2xMatt, Steve) for the op25 and op25-legacy repositories on git.osmocom.org. Since then, you should be able to push to gitosis@git.osmocom.org:op25.git and gitosis@git.osmocom.org:op25-legacy.git, respectively.
I just re-synced all branches/HEADs from the op25.git on op25.osmocom.org to git.osmocomorg/op25 today.
Also, Holger has now root ssh access to op25.osmocom.org, from where he has access to the trac database and all attachmetns. Let's hope he has time and is still willing to do the redmine conversion.
Once that conversion is done, I think we can update DNS and install a http redirect from http://op25.osmocom.org/ to http://osmocom.org/projects/op25 and finally shut down the old unstable jail with its aging trac installation.
Until then, it would be great if you could verify your redmine accounts on https://osmocom.org/ and your ssh access to the gitosis@git.osmocom.org repositories (you could just push some branch/tag and then delete it again to verify).
Thanks for all your help. Once OP25 runs on the same infrastructure as the rest of osmocom, the infrastructure will be maintained again.
Regards, Harald
Hi Harald and Holger,
This is great news, please let us know how it progresses, we are very excited to move off our old unstable infrastructure and onto the new osmocom platform.
Many thanks again, and happy new year guys!
Cheers, Matt
On 7 January 2017 at 22:18, Harald Welte laforge@gnumonks.org [op25-dev] < op25-dev@yahoogroups.com> wrote:
Dear OP25 developers,
On Thu, Apr 07, 2016 at 10:14:41AM +1000, Steve Glass wrote:
Yeah, those are the only services we need. I am delighted that we're finally making the move :)
I'm sorry that I dropped the ball on Holger for migration of the trac to redmine back in April/May 2016 :/
I've just resurrected the op25 container one more time, and installed a cron-job that restarts the container once every night (1am GMT), to make sure the content is reachable without any manual intervention by me.
Back last year, the op25-legacy svn had been converted and imported to git.osmocom.org (see http://git.osmocom.org/op25-legacy/). Also, the op25 git repo had been imported at http://git.osmocom.org/op25/
Also back then, I added your ssh public keys (Max, 2xMatt, Steve) for the op25 and op25-legacy repositories on git.osmocom.org. Since then, you should be able to push to gitosis@git.osmocom.org:op25.git and gitosis@git.osmocom.org:op25-legacy.git, respectively.
I just re-synced all branches/HEADs from the op25.git on op25.osmocom.org to git.osmocomorg/op25 today.
Also, Holger has now root ssh access to op25.osmocom.org, from where he has access to the trac database and all attachmetns. Let's hope he has time and is still willing to do the redmine conversion.
Once that conversion is done, I think we can update DNS and install a http redirect from http://op25.osmocom.org/ to http://osmocom.org/projects/op25 and finally shut down the old unstable jail with its aging trac installation.
Until then, it would be great if you could verify your redmine accounts on https://osmocom.org/ and your ssh access to the gitosis@git.osmocom.org repositories (you could just push some branch/tag and then delete it again to verify).
Thanks for all your help. Once OP25 runs on the same infrastructure as the rest of osmocom, the infrastructure will be maintained again.
Regards, Harald
--
- Harald Welte laforge@gnumonks.org http://laforge.gnumonks.org/
============================================================
"Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
Hello Harald Thanks for your help in moving this forward. Just to respond to one thing that you mentioned
Until then, it would be great if you could verify your redmine accounts on https://osmocom.org/ and your ssh access to the gitosis@git.osmocom.org repositories (you could just push some branch/tag and then delete it again to verify).
I was able to push a change to the git repo on gitosis@ but wasn't able to login to redmine. I tried username 'max' with the old Trac password for that account - no luck.
Max
On Saturday, January 7, 2017 8:38 PM, "Matt Ames matt.ames7bc@gmail.com [op25-dev]" op25-dev@yahoogroups.com wrote:
Hi Harald and Holger, This is great news, please let us know how it progresses, we are very excited to move off our old unstable infrastructure and onto the new osmocom platform. Many thanks again, and happy new year guys! Cheers, Matt
On 7 January 2017 at 22:18, Harald Welte laforge@gnumonks.org [op25-dev] op25-dev@yahoogroups.com wrote:
Dear OP25 developers,
On Thu, Apr 07, 2016 at 10:14:41AM +1000, Steve Glass wrote:
Yeah, those are the only services we need. I am delighted that we're finally making the move :)
I'm sorry that I dropped the ball on Holger for migration of the trac to redmine back in April/May 2016 :/
I've just resurrected the op25 container one more time, and installed a cron-job that restarts the container once every night (1am GMT), to make sure the content is reachable without any manual intervention by me.
Back last year, the op25-legacy svn had been converted and imported to git.osmocom.org (see http://git.osmocom.org/op25- legacy/). Also, the op25 git repo had been imported at http://git.osmocom.org/op25/
Also back then, I added your ssh public keys (Max, 2xMatt, Steve) for the op25 and op25-legacy repositories on git.osmocom.org. Since then, you should be able to push to gitosis@git.osmocom.org:op25. git and gitosis@git.osmocom.org:op25- legacy.git, respectively.
I just re-synced all branches/HEADs from the op25.git on op25.osmocom.org to git.osmocomorg/op25 today.
Also, Holger has now root ssh access to op25.osmocom.org, from where he has access to the trac database and all attachmetns. Let's hope he has time and is still willing to do the redmine conversion.
Once that conversion is done, I think we can update DNS and install a http redirect from http://op25.osmocom.org/ to http://osmocom.org/projects/ op25 and finally shut down the old unstable jail with its aging trac installation.
Until then, it would be great if you could verify your redmine accounts on https://osmocom.org/ and your ssh access to the gitosis@git.osmocom.org repositories (you could just push some branch/tag and then delete it again to verify).
Thanks for all your help. Once OP25 runs on the same infrastructure as the rest of osmocom, the infrastructure will be maintained again.
Regards, Harald
On Wed, Apr 06, 2016 at 10:24:55AM +0200, Holger Freyther wrote:
could you send me the trac-db while the system is reachable?
will do so off-list.
I will take care of importing all of that into a separte (op25-legacy?) git repository on git.osmocom.org meanwhile, to preserve the legacy.
I can set-up a read-only svn as well. Alternatively you can use the "github" svn import (git svn clone is not too good at converting more complicated history). Or KDEs svn2git utility (or my hack on top of it that I used for work at the university). Or don't care too much about the entire history.
The op25-legacy svn-git conversion is already done, I'm about to push it to git.osmocom.org.
redmine on projects.osmocom.org has now a (not yet public) OP25 project with the user accounts of matt, max and stevie. It already has the git repositories on git.osmocom.org configured as 'repositories'.
-
Harald Welte laforge＠gnumonks.org [op25-dev] -
ikjtel ikj1234i＠yahoo.com [op25-dev]
-
Matt Ames matt.ames7bc＠gmail.com [op25-dev]
-
Steve Glass stevie.glass＠gmail.com [op25-dev]