Menu
▾
▴
nagios-devteam — Nagios Core Development Team List
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(19) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
(12) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Andreas E. <ae...@op...> - 2010-04-29 17:53:28
|
On 04/29/2010 05:25 PM, Ton Voon wrote: > > On 29 Apr 2010, at 16:16, Andreas Ericsson wrote: > >> git pull git://git.op5.org/nagios.git dev >> >> and you should get the fix. It was a work-in-progress commit that >> accidentally got published. I shall strive to be more careful in >> the future. > > That fixed it, thanks. > > The build now works, but the tests don't. The perl tests are okay, but > the C tests don't compile. I'm guessing your cleanups have moved some > files around? > Yes. Common code has been put in common/shared.c, which compiles just once to common/shared.o. Doing an overhaul of the buildsystem is something I'm sort of working on at the same time. Primarily, I want cgi's and daemon to use the same set of files for shared functions. That's why the microstubs for functions that don't make sense for cgi's to run are in cgiutils.c. A half-clever linker will optimize the calls away when running with -O1 or above, so it's quite alright to do things that way, really. > make test-tap > > Brings compile errors. Admittedly, the way I'm doing this is a bit > fragile. I'm open for ideas on how to do this better (move to base/ so > that gets compiled with same options as nagios executable?). > Most of the tests I run with other projects are being run against one specific api, although they often use each other quite a lot. This makes it pretty easy to just add a UTIL_OBJS variable (or some such) to the makefile and make sure all .o files required for linking are listed there. > Shall we bring this conversation onto nagios-devel? > Perhaps. I don't care very much one way or the other, but I guess it'd be good to let people know that things are moving forward again so they can run the new stuff and build on top of it. I'll get an announcement out. -- Andreas Ericsson and...@op... OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. |
|
From: Ton V. <to...@ma...> - 2010-04-29 15:25:43
|
On 29 Apr 2010, at 16:16, Andreas Ericsson wrote: > git pull git://git.op5.org/nagios.git dev > > and you should get the fix. It was a work-in-progress commit that > accidentally got published. I shall strive to be more careful in > the future. That fixed it, thanks. The build now works, but the tests don't. The perl tests are okay, but the C tests don't compile. I'm guessing your cleanups have moved some files around? make test-tap Brings compile errors. Admittedly, the way I'm doing this is a bit fragile. I'm open for ideas on how to do this better (move to base/ so that gets compiled with same options as nagios executable?). Shall we bring this conversation onto nagios-devel? Ton |
|
From: Andreas E. <ae...@op...> - 2010-04-29 15:16:22
|
On 04/29/2010 03:42 PM, Ton Voon wrote: > > On 29 Apr 2010, at 14:29, Andreas Ericsson wrote: > >>> I'm trying to merge in your cleanups which is in origin/dev (?). >>> But I >>> get: >>> >>> $ git merge origin/dev >>> error: Untracked working tree file 'include/cgiutils.h' would be >>> overwritten by merge. >>> fatal: merging of trees 6e873029f92756295b62976258d55691a9aee329 and >>> 3445b4fc91fbd54c1387f51e6c321305abc0a546 failed >>> Merge with strategy recursive failed. >>> >>> What does this mean and how do I resolve? >>> >> >> It means I've added a file to version control that is in your >> worktree but not tracked by git in your end. Do a "make distclean" >> first and it should work, or just remove it manually. That one is >> a generated file before my cleanups, and a tracked file after >> them, and git refuses to overwrite non-tracked content since it >> would mean you'd lose work with no chance of restoring it. > > That has fixed it thanks. I've added a note for myself at http://wiki.nagios.org/index.php/GIT_Introduction#Troubleshooting > > > With this merge, it looks like things are failing to compile: > > $ make nagios > cd ./base&& make > gcc -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o macros-base.o ../common/ > macros.c > ../common/macros.c: In function ‘init_macrox_names’: > ../common/macros.c:2512: error: ‘HOSTNAME’ undeclared (first use in > this function) > ../common/macros.c:2512: error: (Each undeclared identifier is > reported only once > ../common/macros.c:2512: error: for each function it appears in.) > ../common/macros.c:2513: error: ‘HOSTALIAS’ undeclared (first use in > this function) > .... > > I can't see a macro definition for HOSTNAME anywhere. Have you missed > a file? > No, but a hash-sign in common/macros.c. Issue git pull git://git.op5.org/nagios.git dev and you should get the fix. It was a work-in-progress commit that accidentally got published. I shall strive to be more careful in the future. -- Andreas Ericsson and...@op... OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. |
|
From: Ton V. <to...@ma...> - 2010-04-29 13:42:49
|
On 29 Apr 2010, at 14:29, Andreas Ericsson wrote: >> I'm trying to merge in your cleanups which is in origin/dev (?). >> But I >> get: >> >> $ git merge origin/dev >> error: Untracked working tree file 'include/cgiutils.h' would be >> overwritten by merge. >> fatal: merging of trees 6e873029f92756295b62976258d55691a9aee329 and >> 3445b4fc91fbd54c1387f51e6c321305abc0a546 failed >> Merge with strategy recursive failed. >> >> What does this mean and how do I resolve? >> > > It means I've added a file to version control that is in your > worktree but not tracked by git in your end. Do a "make distclean" > first and it should work, or just remove it manually. That one is > a generated file before my cleanups, and a tracked file after > them, and git refuses to overwrite non-tracked content since it > would mean you'd lose work with no chance of restoring it. That has fixed it thanks. I've added a note for myself at http://wiki.nagios.org/index.php/GIT_Introduction#Troubleshooting With this merge, it looks like things are failing to compile: $ make nagios cd ./base && make gcc -g -O2 -DHAVE_CONFIG_H -DNSCORE -c -o macros-base.o ../common/ macros.c ../common/macros.c: In function ‘init_macrox_names’: ../common/macros.c:2512: error: ‘HOSTNAME’ undeclared (first use in this function) ../common/macros.c:2512: error: (Each undeclared identifier is reported only once ../common/macros.c:2512: error: for each function it appears in.) ../common/macros.c:2513: error: ‘HOSTALIAS’ undeclared (first use in this function) .... I can't see a macro definition for HOSTNAME anywhere. Have you missed a file? Ton |
|
From: Andreas E. <ae...@op...> - 2010-04-29 13:29:13
|
On 04/29/2010 03:08 PM, Ton Voon wrote: > > On 29 Apr 2010, at 13:57, Andreas Ericsson wrote: > >> >> Great. So long as we base everything on a common ancestor that should >> work just fine, and it appears as though we do, since we have the >> same commit-id from the cvs import. > > Yes, I used your op5 git repo for nagios. > Ah, nice. I'll make sure to keep that one up-to-date then. >> >> One nit though; Could you add some more text to the commit messages >> describing what a patch/commit does and why that's a good idea? >> >> Viewing the log right now, there are quite a few commits I really >> can't get the hang of. fd77c2e4dfd2fb474e7ac9bc28da5ccba94114fc is >> my favourite. Besides, if I can't figure out why a change is a good >> thing, it's likely you won't be able to either in a year or so. > > That's a fair point. I'll try to be more verbose in the commit messages. > Thanks. It gets important when others want to understand what's being done, and why (with "other" possibly being ones future self). > I'm trying to merge in your cleanups which is in origin/dev (?). But I > get: > > $ git merge origin/dev > error: Untracked working tree file 'include/cgiutils.h' would be > overwritten by merge. > fatal: merging of trees 6e873029f92756295b62976258d55691a9aee329 and > 3445b4fc91fbd54c1387f51e6c321305abc0a546 failed > Merge with strategy recursive failed. > > What does this mean and how do I resolve? > It means I've added a file to version control that is in your worktree but not tracked by git in your end. Do a "make distclean" first and it should work, or just remove it manually. That one is a generated file before my cleanups, and a tracked file after them, and git refuses to overwrite non-tracked content since it would mean you'd lose work with no chance of restoring it. -- Andreas Ericsson and...@op... OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. |
|
From: Ton V. <to...@ma...> - 2010-04-29 13:08:54
|
On 29 Apr 2010, at 13:57, Andreas Ericsson wrote: > > Great. So long as we base everything on a common ancestor that should > work just fine, and it appears as though we do, since we have the > same commit-id from the cvs import. Yes, I used your op5 git repo for nagios. > > One nit though; Could you add some more text to the commit messages > describing what a patch/commit does and why that's a good idea? > > Viewing the log right now, there are quite a few commits I really > can't get the hang of. fd77c2e4dfd2fb474e7ac9bc28da5ccba94114fc is > my favourite. Besides, if I can't figure out why a change is a good > thing, it's likely you won't be able to either in a year or so. That's a fair point. I'll try to be more verbose in the commit messages. I'm trying to merge in your cleanups which is in origin/dev (?). But I get: $ git merge origin/dev error: Untracked working tree file 'include/cgiutils.h' would be overwritten by merge. fatal: merging of trees 6e873029f92756295b62976258d55691a9aee329 and 3445b4fc91fbd54c1387f51e6c321305abc0a546 failed Merge with strategy recursive failed. What does this mean and how do I resolve? Ton |
|
From: Andreas E. <ae...@op...> - 2010-04-29 12:58:01
|
On 04/29/2010 02:30 PM, Ton Voon wrote: > > On 16 Apr 2010, at 16:15, Andreas Ericsson wrote: > >> On 04/16/2010 04:08 PM, Ton Voon wrote: >>> >>> Andreas, can you update >>> http://wiki.nagios.org/index.php/GIT_Introduction with a few >>> pointers on >>> how to start? I'm happy to update as I get further. >>> >> >> Done. There's really far too many manuals and tutorials online already >> for there to be any point for me to create another, but I've added >> some >> useful tips and aliases that I tend to more or less live by and added >> some links to the more useful tutorials out there. >> >> I've ordered them the way I think it's most beneficial, long-term, to >> read them. >> >> I've also upgraded devteams.nagios.org with a fresh git and yum >> upgrade, >> so it's ticking nicely (not that it didn't before, but what the hell). > > Thanks for the doc updates. > > I've decided to use github as the repo for opsview-nagios simply > because it is easier for me to manage, so I've committed a couple of > new features in there: http://github.com/tonvoon/opsview-nagios > Great. So long as we base everything on a common ancestor that should work just fine, and it appears as though we do, since we have the same commit-id from the cvs import. One nit though; Could you add some more text to the commit messages describing what a patch/commit does and why that's a good idea? Viewing the log right now, there are quite a few commits I really can't get the hang of. fd77c2e4dfd2fb474e7ac9bc28da5ccba94114fc is my favourite. Besides, if I can't figure out why a change is a good thing, it's likely you won't be able to either in a year or so. If you detest using the editor for each commit, you can pass multiple -m "message" options to "git commit". Each -m parameter will be added as a separate paragraph in the commit message. Thanks -- Andreas Ericsson and...@op... OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. |
|
From: Ton V. <to...@ma...> - 2010-04-29 12:30:55
|
On 16 Apr 2010, at 16:15, Andreas Ericsson wrote: > On 04/16/2010 04:08 PM, Ton Voon wrote: >> >> Andreas, can you update >> http://wiki.nagios.org/index.php/GIT_Introduction with a few >> pointers on >> how to start? I'm happy to update as I get further. >> > > Done. There's really far too many manuals and tutorials online already > for there to be any point for me to create another, but I've added > some > useful tips and aliases that I tend to more or less live by and added > some links to the more useful tutorials out there. > > I've ordered them the way I think it's most beneficial, long-term, to > read them. > > I've also upgraded devteams.nagios.org with a fresh git and yum > upgrade, > so it's ticking nicely (not that it didn't before, but what the hell). Thanks for the doc updates. I've decided to use github as the repo for opsview-nagios simply because it is easier for me to manage, so I've committed a couple of new features in there: http://github.com/tonvoon/opsview-nagios Ton |
|
From: Andreas E. <ae...@op...> - 2010-04-21 15:27:25
|
Ahoy. I've just committed three patches, removing a lot of old and dead code, as well as de-duplicating about 500LoC from base/utils.c and cgi/cgiutils.c, and their respective header files. These patches are purely cleanup (and sorely needed ones too). Make sure you have them in case you want to add stuff on top. I've pushed it to the git repo at devteams.nagios.org as well as to git.op5.org, and I've done my work in the 'dev' branch. I'll re-arrange it a bit so we can commit to master without risking fucking up the continuous cvs imports in the future. -- Andreas Ericsson and...@op... OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. |
|
From: Andreas E. <ae...@op...> - 2010-04-16 15:15:40
|
On 04/16/2010 04:08 PM, Ton Voon wrote: > > On 16 Apr 2010, at 15:05, Andreas Ericsson wrote: >> I've got some major work coming in too. I'll be implementing process >> pools that Jean Paul Gabés talked about earlier and getting rid of the >> checkresult file thing in favor of a bidirectional socket and worker- >> daemons instead. >> >> I'll be using the git repository at devteams.nagios.org:~git/nagios.git, >> with some branch I haven't thought up a name for yet. I've tried getting >> my head around CVS again, but I just can't figure out how to get anything >> done with it anymore, so I've given up and decided to get some real work >> done instead. Everything will also be at git://git.op5.org/nagios.git, >> reviewable from http://git.op5.org/git/?p=nagios.git;a=summary (although >> one will have to choose the proper branch to view). >> >> You can use the same repo if you like. Assuming we don't modify the same >> code too much it shouldn't be much of a problem rebasing all the patches >> to a linear history and bringing it all back to the cvs repo later. > > I've given up on CVS too, which is partly why I haven't committed > anything in a new branch. I'd rather invest the time in understanding > how to use git properly. > > Andreas, can you update > http://wiki.nagios.org/index.php/GIT_Introduction with a few pointers on > how to start? I'm happy to update as I get further. > Done. There's really far too many manuals and tutorials online already for there to be any point for me to create another, but I've added some useful tips and aliases that I tend to more or less live by and added some links to the more useful tutorials out there. I've ordered them the way I think it's most beneficial, long-term, to read them. I've also upgraded devteams.nagios.org with a fresh git and yum upgrade, so it's ticking nicely (not that it didn't before, but what the hell). -- Andreas Ericsson and...@op... OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. |
|
From: Ton V. <to...@ma...> - 2010-04-16 14:09:17
|
On 16 Apr 2010, at 15:05, Andreas Ericsson wrote: > I've got some major work coming in too. I'll be implementing process > pools that Jean Paul Gabés talked about earlier and getting rid of the > checkresult file thing in favor of a bidirectional socket and worker- > daemons instead. > > I'll be using the git repository at devteams.nagios.org:~git/ > nagios.git, > with some branch I haven't thought up a name for yet. I've tried > getting > my head around CVS again, but I just can't figure out how to get > anything > done with it anymore, so I've given up and decided to get some real > work > done instead. Everything will also be at git://git.op5.org/nagios.git, > reviewable from http://git.op5.org/git/?p=nagios.git;a=summary > (although > one will have to choose the proper branch to view). > > You can use the same repo if you like. Assuming we don't modify the > same > code too much it shouldn't be much of a problem rebasing all the > patches > to a linear history and bringing it all back to the cvs repo later. I've given up on CVS too, which is partly why I haven't committed anything in a new branch. I'd rather invest the time in understanding how to use git properly. Andreas, can you update http://wiki.nagios.org/index.php/GIT_Introduction with a few pointers on how to start? I'm happy to update as I get further. Ton |
|
From: Andreas E. <ae...@op...> - 2010-04-16 14:05:19
|
On 03/01/2010 02:14 PM, Ton Voon wrote: > > On 29 Jan 2010, at 05:41, Ethan Galstad wrote: > >> Andreas Ericsson wrote: >>> On 01/28/2010 10:07 AM, Ton Voon wrote: >>>> Hi guys! >>>> >>>> I was wondering if we can cut a branch of Nagios? I have some >>>> stuff I >>>> want to add in but should not go into a stable branch. >>>> >>> >>> I whole-heartedly agree with that. >> >> We can. I'll create a new branch you can put new code in. I'd like >> to >> know what would be added before it gets committed, as synchronization >> code might be better suited for an addon outside the core. > > Hi Ethan, > > Can you create that new branch? Or maybe CVS HEAD is the latest > development and you branch off Nagios 3.2 instead. > > I've sent the patch info to nagios-devel and Andreas seems fine with > it, so I'd like to move forward with getting some new commits in. I'll > check with other "controversial" patches on the nagios-devel list (as > per http://wiki.nagios.org/index.php/Nagios_Core_Developer_Guidelines#Patches) > . > I've got some major work coming in too. I'll be implementing process pools that Jean Paul Gabés talked about earlier and getting rid of the checkresult file thing in favor of a bidirectional socket and worker- daemons instead. I'll be using the git repository at devteams.nagios.org:~git/nagios.git, with some branch I haven't thought up a name for yet. I've tried getting my head around CVS again, but I just can't figure out how to get anything done with it anymore, so I've given up and decided to get some real work done instead. Everything will also be at git://git.op5.org/nagios.git, reviewable from http://git.op5.org/git/?p=nagios.git;a=summary (although one will have to choose the proper branch to view). You can use the same repo if you like. Assuming we don't modify the same code too much it shouldn't be much of a problem rebasing all the patches to a linear history and bringing it all back to the cvs repo later. -- Andreas Ericsson and...@op... OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. |
|
From: Ton V. <to...@ma...> - 2010-03-01 14:14:39
|
On 29 Jan 2010, at 05:41, Ethan Galstad wrote: > Andreas Ericsson wrote: >> On 01/28/2010 10:07 AM, Ton Voon wrote: >>> Hi guys! >>> >>> I was wondering if we can cut a branch of Nagios? I have some >>> stuff I >>> want to add in but should not go into a stable branch. >>> >> >> I whole-heartedly agree with that. > > We can. I'll create a new branch you can put new code in. I'd like > to > know what would be added before it gets committed, as synchronization > code might be better suited for an addon outside the core. Hi Ethan, Can you create that new branch? Or maybe CVS HEAD is the latest development and you branch off Nagios 3.2 instead. I've sent the patch info to nagios-devel and Andreas seems fine with it, so I'd like to move forward with getting some new commits in. I'll check with other "controversial" patches on the nagios-devel list (as per http://wiki.nagios.org/index.php/Nagios_Core_Developer_Guidelines#Patches) . Ton |
|
From: Ethan G. <ega...@na...> - 2010-01-29 05:41:58
|
Andreas Ericsson wrote: > On 01/28/2010 10:07 AM, Ton Voon wrote: >> Hi guys! >> >> I was wondering if we can cut a branch of Nagios? I have some stuff I >> want to add in but should not go into a stable branch. >> > > I whole-heartedly agree with that. We can. I'll create a new branch you can put new code in. I'd like to know what would be added before it gets committed, as synchronization code might be better suited for an addon outside the core. > >> Are we switching to git as well? I think 3.2.0 was a dependency. >> > > We are. I've done the conversion but haven't had time to dig into how to > set up the git to cvs autopush and things like that, and unfortunately > sourceforge has no support for git-cvsserver so I'll have to write a > hook script. > No, we are not - at least not yet. :-) With everything I have going on, I can't take the time to learn a new system. FYI, we're going to be hiring a few devs over the next few months, and I'll be bringing them onto the project teams to help out. That means faster bug patches and more activity all around - very exciting for the project. Git is probably the tool of choice, but I don't have the time for it myself just yet. Hop you guys are doing well. - Ethan |
|
From: Andreas E. <ae...@op...> - 2010-01-28 09:49:24
|
On 01/28/2010 10:07 AM, Ton Voon wrote: > Hi guys! > > I was wondering if we can cut a branch of Nagios? I have some stuff I > want to add in but should not go into a stable branch. > I whole-heartedly agree with that. > Are we switching to git as well? I think 3.2.0 was a dependency. > We are. I've done the conversion but haven't had time to dig into how to set up the git to cvs autopush and things like that, and unfortunately sourceforge has no support for git-cvsserver so I'll have to write a hook script. -- Andreas Ericsson and...@op... OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. |
|
From: Ton V. <to...@ma...> - 2010-01-28 09:08:06
|
Hi guys! I was wondering if we can cut a branch of Nagios? I have some stuff I want to add in but should not go into a stable branch. Are we switching to git as well? I think 3.2.0 was a dependency. Ton |
|
From: Ethan G. <ega...@na...> - 2009-06-23 02:16:12
|
Hi Guys - I just cut the 3.1.1 release and published it. I'm delaying an officia switch to git, as well as the switch of indentation indefinitely at this point, as I've got a hundred things on the burner right now. With new websites to launch, support contract stuff, and lots of other up-and-coming goodies, there's no way I can handle a major switch of how things are done. I won't rule out these changes in the future, but the project would be at risk if they were to happen now. Thanks for the work you guys put into this release! - Ethan Galstad |
|
From: Ethan G. <ega...@na...> - 2009-06-22 23:35:04
|
Just do a "ssh root@localhost" and you're in. :-) - Ethan Galstad Ton Voon wrote: > Ethan, > > Was going to setup the nagios tinderbox, but I need root access (to > create the tinderbox2 user and the apache directory area). I can logon > with the ssh key, but I can't run sudo as I don't have a password > setup. Can you set me up with root access? > > Ton > > On 20 May 2009, at 16:49, Ethan Galstad wrote: > >> Ton and Andreas - >> >> You're both setup with access to devteams.nagios.org. I sent email >> instructions a minute ago. >> >> Here's how the server is setup: >> >> 1. The server is running CentOS 5.2 >> >> 2. All websites are stored in /store/websites: >> >> /store/websites/git.nagios.org >> /store/websites/tinderbox.nagios.org >> >> 3. The system is automatically backed up daily and weekly by our VM >> system. Additionally, local scripts backup the MySQL db and /store >> directory daily to localhost. Those local backups are then rsync'ed >> offsite in case really bad things happen. > > > ------------------------------------------------------------------------------ > Are you an open source citizen? Join us for the Open Source Bridge conference! > Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. > Need another reason to go? 24-hour hacker lounge. Register today! > http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org > _______________________________________________ > Nagios-devteam mailing list > Nag...@li... > https://lists.sourceforge.net/lists/listinfo/nagios-devteam |
|
From: Ton V. <to...@ma...> - 2009-06-22 19:35:57
|
Ethan, Was going to setup the nagios tinderbox, but I need root access (to create the tinderbox2 user and the apache directory area). I can logon with the ssh key, but I can't run sudo as I don't have a password setup. Can you set me up with root access? Ton On 20 May 2009, at 16:49, Ethan Galstad wrote: > Ton and Andreas - > > You're both setup with access to devteams.nagios.org. I sent email > instructions a minute ago. > > Here's how the server is setup: > > 1. The server is running CentOS 5.2 > > 2. All websites are stored in /store/websites: > > /store/websites/git.nagios.org > /store/websites/tinderbox.nagios.org > > 3. The system is automatically backed up daily and weekly by our VM > system. Additionally, local scripts backup the MySQL db and /store > directory daily to localhost. Those local backups are then rsync'ed > offsite in case really bad things happen. |
|
From: Ton V. <to...@ma...> - 2009-05-20 16:11:08
|
On 20 May 2009, at 17:00, Ethan Galstad wrote: > > If you still have the info that Hendrik sent you on git, can you put > it > online? I created a new "Developer Documentation" section on the Wiki > for stuff like this: > > http://community.nagios.org/wiki/index.php/Developer_Documentation I've moved the Developer Guidelines from the front page under this Developer Documentation link, where it is more appropriate. > We arrive Tuesday early noon and fly out on Saturday. I think Friday > afternoon will be free for us, but if you're busy we'll just have to > party Thursday night. Which means we should get the git stuff out of > the > way before that happens. :-) :) Ange and I arrive Tuesday early afternoon and we plan on spending a few hours sightseeing. We'll get to the hotel in the early evening. We fly out first thing on Friday though, so not partying for us then :( Ton |
|
From: Ethan G. <ega...@na...> - 2009-05-20 16:01:12
|
Andreas Ericsson wrote: > Ethan Galstad wrote: >> Top posting because its easier. :-) >> > > As the Pope of Nagios, I suspect you can bestow a healthy dose of > absolution on yourself for that ;-) > >> I see your pain with CVS and believe that we should move to git. It >> will take a while for me to get up to speed on git, as I have more than >> a full plate of things to take care of in the next month. >> >> What I would suggest is this: >> >> 1. We make a 3.1.1 release with bugfixes and let people test it out >> 2. After a bit of testing, a 3.2 stable release is made >> 3. After 3.2, we ditch CVS and move to git completely. >> >> There aren't too many more patches that would need to be applied to make >> a 3.1.1 release, so that can probably come out late this week. After a >> 3.2 release we switch to git and proceed on a development path that we >> can all discuss at the conference in two weeks. >> >> Is this a reasonable scenario for you Andreas? >> > > Sounds awesome. It's good to have something to look forward to. > > As for getting up to speed on git, I'd be happy to give you a quick > crash-course when we meet in stockholm. 10 minutes of face-to-face > explanation is probably worth about 20 hours of browsing online > documentation. It'd also give you an insight into how I work with > git, both for Nagios' sake and all of the Nagios-related stuff at > op5, which I'm sure will come in handy at some point. Sounds perfect. If you still have the info that Hendrik sent you on git, can you put it online? I created a new "Developer Documentation" section on the Wiki for stuff like this: http://community.nagios.org/wiki/index.php/Developer_Documentation > > I haven't booked a return train to gothenburg yet. I'm actually > planning on staying in Stockholm over the following weekend to party > with some friends. Depending on your plans we might have plenty > of time even though I suspect much of it will be interrupted by suits > wanting to discuss pieces of paper. With any luck, there's a boat > involved this year too ;-) > We arrive Tuesday early noon and fly out on Saturday. I think Friday afternoon will be free for us, but if you're busy we'll just have to party Thursday night. Which means we should get the git stuff out of the way before that happens. :-) - Ethan Galstad |
|
From: Ethan G. <ega...@na...> - 2009-05-20 15:49:27
|
Ton and Andreas - You're both setup with access to devteams.nagios.org. I sent email instructions a minute ago. Here's how the server is setup: 1. The server is running CentOS 5.2 2. All websites are stored in /store/websites: /store/websites/git.nagios.org /store/websites/tinderbox.nagios.org 3. The system is automatically backed up daily and weekly by our VM system. Additionally, local scripts backup the MySQL db and /store directory daily to localhost. Those local backups are then rsync'ed offsite in case really bad things happen. - Ethan Galstad |
|
From: Andreas E. <ae...@op...> - 2009-05-20 15:10:19
|
Ton Voon wrote: > On 20 May 2009, at 15:57, Andreas Ericsson wrote: > >> Ton, how do you trigger tinderbox builds for the plugins atm? >> With a "release-on-every-push" hook (although to a snapshots >> directory), it would be neat if tinderbox could test-build >> on every push as well. For bonus-points, never publish any >> snapshots that fail building/testing :-) > > The design for tinderbox is that the builds occur on your own server: > you pull the latest snapshot and then you push the reports to the > central tinderbox. I figured that was more likely to get me > contributors than if I said I want to push new builds onto your server > (security, paranoia, etc). > > There are other solutions which do what you say: push packages out to > build servers. Opsera use buildbot internally to push builds to all > our supported platforms. > > I think this depends on how you see this going long term - do you have > your own boxes to build and test on, or do you want to get > contributions from others. > > I erred on the side of others. > A wise decision. Perhaps we can do a mix of both then. I'm sure op5 would sponsor time on 32 and 64 bit buildservers (we already have them, after all), and that would at least provide feedback on the most embarrassing errors. Not that there will be any ofcourse, but still ;-) -- Andreas Ericsson and...@op... OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Register now for Nordic Meet on Nagios, June 3-4 in Stockholm http://nordicmeetonnagios.op5.org/ Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. |
|
From: Ton V. <to...@ma...> - 2009-05-20 15:04:13
|
On 20 May 2009, at 15:57, Andreas Ericsson wrote: > Ton, how do you trigger tinderbox builds for the plugins atm? > With a "release-on-every-push" hook (although to a snapshots > directory), it would be neat if tinderbox could test-build > on every push as well. For bonus-points, never publish any > snapshots that fail building/testing :-) The design for tinderbox is that the builds occur on your own server: you pull the latest snapshot and then you push the reports to the central tinderbox. I figured that was more likely to get me contributors than if I said I want to push new builds onto your server (security, paranoia, etc). There are other solutions which do what you say: push packages out to build servers. Opsera use buildbot internally to push builds to all our supported platforms. I think this depends on how you see this going long term - do you have your own boxes to build and test on, or do you want to get contributions from others. I erred on the side of others. Ton |
|
From: Andreas E. <ae...@op...> - 2009-05-20 14:57:18
|
Ethan Galstad wrote: > Hi Guys - > > I'm setting up a special "devteams.nagios.org" server that will all us > and future teams to host what we need. With this setup, you'd both get > full shell access, which would allow us to have official: > > git.nagios.org > > and > > tinderbox.nagios.org > > If we need something else, let me know and I'll get on it. > Sounds awesome. I'd be happy to take care of git.nagios.org. Ton, how do you trigger tinderbox builds for the plugins atm? With a "release-on-every-push" hook (although to a snapshots directory), it would be neat if tinderbox could test-build on every push as well. For bonus-points, never publish any snapshots that fail building/testing :-) We do autobuilding and a bunch of other stuff on every push at op5. The impact that has on quality of released code and near-deadline stress is just mindboggling, so it would be very neat indeed to get something like that going for Nagios too. -- Andreas Ericsson and...@op... OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Register now for Nordic Meet on Nagios, June 3-4 in Stockholm http://nordicmeetonnagios.op5.org/ Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. |