[dev.icinga.com #12778] Advice against creating zones/endpoints

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12778

Created by tgelf on 2016-09-23 15:28:20 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-11-30 08:06:09 +00:00 (in Redmine)

---

It rarely makes any sense to manually create zones/endpoints. Beginners coming from plain Icinga 2 config often want to start to build their infrastructure with Director exactly like they did before. That way they likely manage it to shoot themselves in the foot while doing completely needless work.

The related forms (Zones, endpoints) should eventually show a big note suggesting to re-read the docs to be absolutely sure that this is really what they need and want.

Changesets

2016-09-29 19:46:21 +00:00 by (unknown) 2a83225

Render the Endpoint to it's Zone parent zone

So you are actually able to define a satellite zone/endpoint from inside the director.

Lower-Knowledge will be deployed via director, higher (or same level) zones and endpoints have to be configured in static local config.

refs #12778

---

Relations:

• relates #12778

[icinga-migration]

Updated by mfrosch on 2016-09-29 19:49:41 +00:00

Yes we should discuss this.

I've added a commit to branch bugfix/render-endpoint-to-parent-zone which would basically allow at least the satellites to be configured via Director.

[icinga-migration]

Updated by mfrosch on 2016-10-26 14:56:34 +00:00

• Relates set to 12988

[icinga-migration]

Updated by copis on 2016-11-30 08:06:09 +00:00

There are some reasons about why this branch are not merged in lastest released director 1.2.0?

I tested the new director_1.2.0 with modified IcingaEndpoing.php and works

[Thomas-Gelf]

Advice has been added long time ago, rendering has been fixed, slightly different than proposed.