Suggestion: CCM and multi-tenancy
Posted: Tue Mar 20, 2012 7:42 pm
Hi Guys,
Something that's been chafing me lately is the way that nagiosQL creates unidirectional links between objects (i.e If you link a host to a hostgroup you can only view the link from the host side). So if you are linking host -> hostgroup you will never be able to get a list of all the hosts that belong to a hostgroup from the CCM, conversely if you were to do it hostgroup -> host you would never be able to see all the hostgroups that a host belongs to.
The suggestion is to display it bidirectionally, now I understand that doing so creates a brand new conundrum (apart from the challenges it presents in the vast amount of additional CCM coding)... when you write the config files which object is the authoritative source so that you don't end up with a definition that links in both directions and makes Nagios fail to start? The best idea I've come up with so far is to add a section that allows you to configure which object in a relationship is authoritative (so either hosts or hostgroups, contacts or contact groups, so on and so forth). Though this has implications of significantly reducing flexibility and probably requires a bit more thought.
I realise this isn't likely to happen any time in the foreseeable future but the more you start seeing large installations the more likely I think you are going to see this come up.
Something that's been chafing me lately is the way that nagiosQL creates unidirectional links between objects (i.e If you link a host to a hostgroup you can only view the link from the host side). So if you are linking host -> hostgroup you will never be able to get a list of all the hosts that belong to a hostgroup from the CCM, conversely if you were to do it hostgroup -> host you would never be able to see all the hostgroups that a host belongs to.
The suggestion is to display it bidirectionally, now I understand that doing so creates a brand new conundrum (apart from the challenges it presents in the vast amount of additional CCM coding)... when you write the config files which object is the authoritative source so that you don't end up with a definition that links in both directions and makes Nagios fail to start? The best idea I've come up with so far is to add a section that allows you to configure which object in a relationship is authoritative (so either hosts or hostgroups, contacts or contact groups, so on and so forth). Though this has implications of significantly reducing flexibility and probably requires a bit more thought.
I realise this isn't likely to happen any time in the foreseeable future but the more you start seeing large installations the more likely I think you are going to see this come up.