----- Original Message ----- > From: "David Lutterkort" <[email protected]> > To: "puppet-dev" <[email protected]> > Sent: Saturday, 7 May, 2016 01:32:45 > Subject: Re: [Puppet-dev] metaparam question
> On Fri, May 6, 2016 at 1:02 PM, R.I.Pienaar <[email protected]> wrote: > >> Those checks you have in AO are good but the barrier to entry is quite >> high on >> making those I felt > > > Understood, and not trying to argue, but because I am curious: what's the > barrier to entry that keeps you from using that mechanism ? Not sure if you > know, but you can use service resources without writing out full > applications or an environment catalog, i.e. you can do stuff like > > define db { ... } > Db produces Sql { .. } > > define web { ... } > > node db_node { > db { one: export => Sql[one] } > } > > node web_node { > web { one: require => Sql[one] } > } > > which does little more than putting that sql into web_node's catalog, which > would then trigger running the check as a gate for applying web. > > Sensu/Nagios can then fish the Sql out of both db_node's and web_node's > catalog and do their own checking. > > I am mostly curious about the barrier to entry to see if there is anything > we can do to lower it. hmm, so that seems very verbose and how to implement the SQL check is also quite a task. The verbosity is because you're modelling relationships across nodes of course I do not want to do that - these specific checks are not for cross node checks and as in recent emails I will not use puppetserver as long as operability features are a paid feature, so those are not what I am after. My needs for checks are literally to augment the: service{"x": ensure => running} this will do 'service x status' equiv, I want it to do additional checks and I want those checks to adhere to existing "standards" which might include metrics and such. Do you have an example of using the new check framework for this purpose? -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/264011150.21817.1462693123637.JavaMail.zimbra%40devco.net. For more options, visit https://groups.google.com/d/optout.
