SV: Nagios 2.0 stable

[Aaron Carr]

I and my direct manager share your affinity to open source, however,
when you're part of an organization that has 190+ subsidiaries
(totally over 100K people), you either do what the "standards" group
tells you to do, or you're shown the door.  The only reason I was
allowed to implement Nagios in this environment is because the
standards group has yet to determine a path forward for monitoring. 
One week it's OpenView, the next it's Tivoli, the next it's NetIQ.  So
we've deployed this until someone makes the final decision on which
way to go.  That still doesn't keep us safe from the *no beta
software* rule.  So we do what we must to get by.

In this environment, the only way that's going to change is to get
someone more open source friendly into the standards group.

Hopefully anyone else reading this will take it into consideration
when you're out doing job interviews.  It may not be a deciding factor
for you in what position you do/don't accept, but it'll definitely be
good to know the stance of your  future employer regarding open
source.

Aaron


On Wed, 23 Mar 2005 10:43:44 -0600, jeff vier
<boinger at tradingtechnologies.com> wrote:
> On Wed, 2005-03-23 at 10:24 -0500, Aaron Carr wrote:
> > While I understand your statement, and for the most part, agree with
> > the underlying intent, some of us are forced to care.
> >
> > At the moment, I'm working for a fortune 100 company.  I would be
> > crucified if I used a *beta* software in a production capacity.  This
> > company has just barely allowed Linux, and several other well known
> > open source applications (Apache, Tomcat)  for use to begin with.
> >
> > For those of us in environments such as this, we *must* wait until the
> > beta is declared successful, and that tag is removed from the version.
> >
> > Does that mean that there won't be bugs?  Of course not.  Does that
> > mean that the processes for support or bugfixes change?  Again, of
> > course not.  That's the just the rules in places like this.
> 
> edit the code and make it say "stable" ;)
> 
> Okay, I see your point.
> 
> I'll amend my opinion to begin "Unless it's a matter of policy..."
> 
> I will say, though, I am very glad I don't have to be stifled by such
> arbitrariness.  I am expected to provide the best there is to offer, not
> provide it in any certain way.  A major pet peeve of mine (such that I
> would be very actively looking for work should it occur at this point in
> my career) is someone who doesn't know any better (often referred to as
> "management") telling me *what* to implement, as opposed to what the end
> goal is.  I've been doing this a long time - I am fully capable of
> determining the right tool for the job.
> 
> Also, *very* fortunately, my boss is a strong OSS believer (to the
> occasional dismay of some of the higher-ups) and I don't ever have to
> justify what tools I'm using.  I just do it, and show the results.
> 
> --boinger
> 
> 
> > On Wed, 23 Mar 2005 09:05:44 -0600, jeff vier
> > <boinger at tradingtechnologies.com> wrote:
> > > On Wed, 2005-03-23 at 11:39 +0100, Bergström Sebastian wrote:
> > > > I realise that my question is unclear. I'm refering to the fact that 2.0 still is in beta.
> > > > We are running v.1.2 currently and are interested in the v.2.0.
> > > >
> > > > I'm wondering if anyone has an idea of how much time it might take before 2.0 can go into a stable (non-beta) state.
> > > >
> > > > Any idea?
> > >
> > > To put it bluntly: Who Cares?
> > >
> > > There are so many of us running it in production (I, myself, have been
> > > doing so since "alpha"), isn't that good enough?
> > >
> > > There will always be bugs, no matter what you call it (alpha, beta, pr,
> > > rc, gold, etc).
> > >
> > > In my, and I'm sure many others', experience, super-pre-double-alpha
> > > code from a nice community-supported project like this is still going to
> > > have less bugs than anything similar from Microsoft no matter how many
> > > "final" versions they have.
> > >
> > > And if something major does come up, there's usually a fix/work-around
> > > in a few hours or days, not weeks or months.
> > >
> > > So, just run it.  If you don't like it, I'll buy you a coke.
> > >
> > > --boinger
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
> > > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
> > > for the chance to win $25,000 and application distribution. Enter today at
> > > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
> > > _______________________________________________
> > > Nagios-users mailing list
> > > Nagios-users at lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > > ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
> > > ::: Messages without supporting info will risk being sent to /dev/null
> > >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
> > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
> > for the chance to win $25,000 and application distribution. Enter today at
> > http://ads.osdn.com/?ad_idh82&alloc_id148&op=click
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
> > ::: Messages without supporting info will risk being sent to /dev/null
> 
>


-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_idh83&alloc_id149&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null