tyler.durden/icingaweb2-module-director
1
0
Fork 0
mirror of https://github.com/Icinga/icingaweb2-module-director.git synced 2025-07-27 07:44:05 +02:00
Code Issues Packages Projects Releases Wiki Activity

doc/agents: link images, complete text

Browse Source
This commit is contained in:
Thomas Gelf 2016-04-17 18:20:20 +02:00
parent f995f4e881
commit c1b5cb1f66
1 changed files with 52 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

53
doc/24-Working-with-agents.md
View File

@ -7,6 +7,7 @@ log settings. There may always be reasons for a completely custom-made
configuration. I'd however strongly suggest to give the Director-assisted configuration. I'd however strongly suggest to give the Director-assisted
variant at least a try first. It might safe you a lot of headaches. variant at least a try first. It might safe you a lot of headaches.
Preparation Preparation
----------- -----------
@ -15,6 +16,8 @@ object. This requires you to create an "Icinga Agent" template. You
could name it exactly like that, it's important to use meaningful names could name it exactly like that, it's important to use meaningful names
for your templates. for your templates.
![Create an Agent template](screenshot/director/24-agents/2401_agent_template.png)
As long as you're not using Satellite nodes a single Agent zone is all As long as you're not using Satellite nodes a single Agent zone is all
you need. Otherwise you should create one Agent template per satellite you need. Otherwise you should create one Agent template per satellite
zone. If you want to move an Agent to a specific zone just assign it zone. If you want to move an Agent to a specific zone just assign it
@ -24,6 +27,54 @@ the correct template and you're all done.
Usage Usage
----- -----
Well, create a host, choose an Agent template, that's it:
![Create an Agent-based host](screenshot/director/24-agents/2402_create_agent_based_host.png)
Once you import the "Icinga Agent" template you'll see a new "Agent" tab. Once you import the "Icinga Agent" template you'll see a new "Agent" tab.
It tries to assist you with the initial Agent setup by showing a sample It tries to assist you with the initial Agent setup by showing a sample
config config:
![Agent instructions 1](screenshot/director/24-agents/2403_show_agent_instructions_1.png)
![Agent instructions 2](screenshot/director/24-agents/2404_show_agent_instructions_2.png)
The preview shows that the Icinga Director would deploy multiple objects
for your newly created host:
![Agent preview](screenshot/director/24-agents/2405_agent_preview.png)
Create Agent-based services
---------------------------
Similar game for services that should run on your Agents. First create a
template with a meaningful name and define that Services inheriting from
this template should run on your Agents.
![Agent-based service](screenshot/director/24-agents/2406_agent_based_service.png)
Please do not set a cluster zone, as this would rarely be necessary.
Agent-based services will always be deployed to their Agent's zone by
default. All you need to do now for services that should be executed
on your Agents ist importing that template:
![Agent-based load check](screenshot/director/24-agents/2407_create_agent_based_load_check.png)
Config preview shows that everything works as expected:
![Agent-based service preview](screenshot/director/24-agents/2409_agent_based_service_rendered_for_host.png)
It's perfectly valid to assign services to host templates. Look how the
generated config differs now:
![Agent-based service assigned to host template](screenshot/director/24-agents/2410_agent_based_service_rendered_for_host_template.png)
While a service added to a host template are implicitely rendered as
assign rules, you could of course also use your `Agent-based service`
template in custom apply rules:
![Agent-based service applied](screenshot/director/24-agents/2411_assign_agent_based_service.png)