<div class="gmail_quote">On Tue, May 17, 2011 at 2:27 PM, Andreas Ericsson <<a href="mailto:ae@op5.se">ae@op5.se</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Ahoy (again). [... service sets] </blockquote><div> Hi, Why not use a "service template on host template" feature instead? The idea is near the second one you proposed. If you add an host_name to a service that is a template, it will generate such service for all hosts that will use this template. So when all your services are defined and lined in the good host templates you will defined : define host { use Linux, Oracle, WhatEver } And the Linux, Oracle, WhatEver are regular host templates, with some services templates linked for each of them. It's more natural for users to think about "templates" than to use a new property. So for example the Linux template will add linux admins as contacts and will add all Linux standard services checks (/, /var, memory, swap,...). We already got all elements we need (template on template is not allowed, so there is no risk in breaking existing configuration), it will be easier for configuration tools than a new object. It will be just like your solution N°2 a little more hard to exchange such "sets" (but in the sample configuration we can just put a configuration file by sets for example). It's what we add in Shinken, and it work quite well :) Jean </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> -- Andreas Ericsson <a href="mailto:andreas.ericsson@op5.se">andreas.ericsson@op5.se</a> OP5 AB <a href="http://www.op5.se" target="_blank">www.op5.se</a> Tel: <a href="tel:%2B46%208-230225" value="+468230225">+46 8-230225</a> Fax: <a href="tel:%2B46%208-230231" value="+468230231">+46 8-230231</a> </blockquote></div>