nagios in debian: 2.x, and plans for support of 1.x?

[sean finney]

hey folks,

now that debian sarge has been released(!), i'm going to start making
some headway towards packaging 2.x pre-release packages in debian's
experimental archive.  however, off the top of my head two issues remain
unresolved that i'll need some input on:

- after 2.x is released, will 1.x still be supported at least in bugfix
  and security related patches?  any idea for how long?

- using the NEB api, is it possible (using possibly not-yet-existing
  code) to get the anything close to the level of support for the 1.x
  db status databases?

the answers to both of these questions will impact significantly the
way in which nagios exists in debian.  there are a couple of options
that i'm considering:

- per-version packages, no upgrade path.  nagios 1.x will continue to
  exist in parallel to the 2.x series of packages, and no attempt is
  made to upgrade users from 1.x to 2.x
- per-version packages, upgrade path.  similar to above, but a set
  of scripts exist to either automatically or manually help upgrade from
  1.x to 2.x.
- one package, upgrade path.  only one major release of nagios exists[1],
  and the helper scripts do whatever is necessary to make an upgrade
  path.

for the "upgrade path", that would include either some level of support
for the db flavored 1.x series, or at the least the ability to dump the
data out of the database into standard configuration/data files.  the
latter i could probably handle on my own (and i'd post whatever i hacked
together), but i don't know if i have the time to commit to the former,
at least by myself.  



thanks for your time,

	sean

[1] of course there would still exist a 1.x version in debian sarge
    until the next stable release, whenever that happens.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20050607/3d8c93f2/attachment.sig>