Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Jun 2014 11:38:52 +0200
From:      Lars Engels <lars.engels@0x20.net>
To:        Warren Block <wblock@wonkity.com>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: [CFT]: net-mgmt/icinga2
Message-ID:  <20140629093852.GN53663@e-new.0x20.net>
In-Reply-To: <alpine.BSF.2.11.1406282132080.23711@lightning.wonkity.com>
References:  <alpine.BSF.2.11.1406282132080.23711@lightning.wonkity.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--/JIF1IJL1ITjxcV4
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jun 28, 2014 at 09:49:52PM -0600, Warren Block wrote:
> I've just been setting this up, and had a question and a couple of notes.
>=20
> Originally, I just installed icinga2.  The icinga2 port does not depend o=
n=20
> icinga, but appears to need it.  Is this really a dependency, or are the=
=20
> two ports meant to be separate?

Icinga 2 itself doesn't need a web interface to work. The Icinga 1 port
includes the classic (cgi) web interface which can be used for Icinga 2,
so it's not a hard dependency.
When I find the time I'm going to create a new port for the classic web
interface.

>=20
> The icinga.conf-sample does not appear to be installed anywhere by the=20
> current port.  It can be found in the staging directory,
> stage/usr/local/share/examples/icinga/apache22/.

It's installed by the Icinga 1 port. From pkg-plist:
%%PORTEXAMPLES%%%%EXAMPLESDIR%%/apache22/icinga.conf-sample

Maybe you have NO_PORTEXAMPLES set?

>=20
> The embedded documentation shown is for 1.11, and it's not clear whether=
=20
> the Javascript client for icinga 2 is available, or whether it will make=
=20
> the CGI interface unnecessary.  Actually, given the config file, and both=
=20
> versions installed, the older version might be the one that is running.  =
I=20
> have not experimented with it much yet.

Yes, the classic web interface still links to the Icinga 1 docs. I think
this should be fixed upstream, so I created a bug report.

Apart from the Classic UI there are two other interfaces for Icinga.
Icinga Web and Icinga Web 2.x. The former isn't too good and will be
deprecated eventually.  The latter is much more straight forward but
isn't ready for production yet.

>=20
> Thank you for your work on this!

Thanks for testing it. :)

--/JIF1IJL1ITjxcV4
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQF8BAEBCgBmBQJTr96sXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF
NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1tVasIALU84w7msLuuZwDbcuHkZm5v
1eL6WumLBdpjmufIQtrOIqTmF5i7UdI13usB2YAohCESqR3pTCmB9kZQ0aOofVE5
Pqa3BWbFIs4Qh1JRVAzt2gmnNo/UjUHIM4K3JU3vHUs1fTGKQ3wHwJEp++y1Vf1b
J+NAkT0GSrjLENZ/G52rst3hScNSE0C1A/0YPDHNmqfYDFBcMZCGSRaSOWEbQG0o
XYtDOlF7iIWOc4WsciNYslOB+9h5mmuf8TNeadN4GuGKtknI0wH8vaRAelcWpfcE
ZEO2tyReNJpbijZlz3bRu6DBbAVEqOqyRgqzudAIkvodcMPeczjRA6DVZ7Staac=
=eNEZ
-----END PGP SIGNATURE-----

--/JIF1IJL1ITjxcV4--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140629093852.GN53663>