On Thu, Feb 17, 2011 at 11:39 PM, Hermann Lauer <
hermann.la...@iwr.uni-heidelberg.de> wrote:
> On Thu, Feb 17, 2011 at 08:41:41PM +0100, nap wrote:
> > >> define poller{
> > >> poller_name poller-monitor
> > >> address test
> > >> port 7879
> > >> poller_tags monitoring,_untagged_
> > >> }
> ...
> > I think the _untagued_ is simpler. It's not a real problem to fix the
> > '_untagued_' tag, because no one will add such tag after all :)
>
> erm, "_untagged_" should be the right english spelling.
> And "None" or "(None)" would probably The Pythonic Way.
>
Yes "None" is a good one :)
> > But I'm wondering how an admin can need a tag and the _untagued_ ? I can
> see
> > two mainly differents ways for tags :
> > * network division : LAN/DMZ for example
> > * OS division : Linux/Windows
> >
> > We can make the _untagued_ the default for tag, won't be a problem. But I
>
> If the poller_tag is not set so far, can't it be left with a test:
> dict.get('poller_tag','_untagged_') in poller_tags
>
> Yes, or even at the arbiter configuration setting.
> > just don't see what problem does it solved ? Hermann do you have an
> example
> > ?
>
> All hosts with shinken daemons on the internet, but only two of them
> (monsrv,poolsrv) with a second network card connected to private
> networks "mon" and "pool".
>
> So the poller on monsrv and poolsrv needs the tag "mon" and "pool", as
> they are the only ones which can test hosts to their private networks,
> but those two pollers should get also all standard internet test stuff
> (untagged) too.
>
> Is that clear enough ?
>
Yes thanks for this example, I didn't think about this :)
So let add this feature. Default poler_tag is "None" and it can be set like
another tag for pollers.
I add it to the trac.
Jean
>
> Thanks,
> Hermann
>
>
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
