Re: [Puppet-dev] Validation Resources

Thanks everyone for your feedback. It sounds like this is a popular idea, and one that leads into further discussion. I've created https://github.com/puppet-community/puppet-healthcheck and asked spredzy to submit the PR against that repo. Cheers, Spencer -- Spencer Krum n...@spencerkrum.co

Re: [Puppet-dev] Validation Resources

On May 14, 2015, at 12:11 PM, Spencer Krum wrote: > > Hi Folks, > > There is currently a PR against stdlib that I am writing to you today > about: https://github.com/puppetlabs/puppetlabs-stdlib/pull/444 > Thanks to Spredzy for making this PR. > > This is tracked in jira: > https://tickets.pupp

Re: [Puppet-dev] Validation Resources

On May 14, 2015, at 4:00 PM, Erik Dalén wrote: > > > > On Thu, 14 May 2015 at 21:45 Trevor Vaughan > wrote: > Hmmwhat about a concept of deferred actions? > > I.e. Try this resource, can't do it, shove it (and it's dependencies) to the > bottom of the stack

Re: [Puppet-dev] Validation Resources

I was actually really hoping for multi-threaded catalog application but I realized that 99% of the time I don't want it because I'm already pegging one processor working on the system. Also, the code complexity that comes with that probably isn't worthwhile. HOWEVER, if we take the idea above and

Re: [Puppet-dev] Validation Resources

On Thursday, May 14, 2015 at 2:45:52 PM UTC-5, Trevor Vaughan wrote: > > Hmmwhat about a concept of deferred actions? > > I.e. Try this resource, can't do it, shove it (and it's dependencies) to > the bottom of the stack and do everything else, then come back to it. > Yes. If there's a re

Re: [Puppet-dev] Validation Resources

On Thu, 14 May 2015 at 21:45 Trevor Vaughan wrote: > Hmmwhat about a concept of deferred actions? > > I.e. Try this resource, can't do it, shove it (and it's dependencies) to > the bottom of the stack and do everything else, then come back to it. > If puppet would think that the provider is

Re: [Puppet-dev] Validation Resources

Hmmwhat about a concept of deferred actions? I.e. Try this resource, can't do it, shove it (and it's dependencies) to the bottom of the stack and do everything else, then come back to it. You could even technically have a method for simply backgrounding that entire resource chain. This sort

Re: [Puppet-dev] Validation Resources

Hey! Do you have a link to that presentation? For a Java spin lock, wouldn't it go something like: * First try -> Wait until timeout * Timeout -> Drop file * Second try -> Notice and remove file * Try again * etc... Trevor On Thu, May 14, 2015 at 3:33 PM, Spencer Krum wrote: > Trevor, > > I

Re: [Puppet-dev] Validation Resources

Trevor, I agree that if you take it to its logical conclusion you end up with semaphores stored in consul and a handful of Puppet resources to interact with them. Dan Bode presented on exactly this (and what doesn't work well about it) at the PDX Puppet Users group last month. I think though that

Re: [Puppet-dev] Validation Resources

On Thu, May 14, 2015 at 12:11 PM, Spencer Krum wrote: > Hi Folks, > > There is currently a PR against stdlib that I am writing to you today > about: https://github.com/puppetlabs/puppetlabs-stdlib/pull/444 > Thanks to Spredzy for making this PR. > > This is tracked in jira: > https://tickets.pupp

Re: [Puppet-dev] Validation Resources

Ugh, sorry all, didn't mean to make that so rant-ish. Anyway, it would seem that you would not want to hold up a catalog compilation or application for this. Instead, you would want to register the check with a service that could drop a queriable entity that could be used by Puppet for making deci

Re: [Puppet-dev] Validation Resources

I'd like to counter this limited use case with my rant about semaphores from five years ago: http://comments.gmane.org/gmane.comp.sysutils.puppet.devel/13039. Followed by the conversation from two years ago. https://projects.puppetlabs.com/issues/16187 What you want is cross-node synchronization

[Puppet-dev] Validation Resources

Hi Folks, There is currently a PR against stdlib that I am writing to you today about: https://github.com/puppetlabs/puppetlabs-stdlib/pull/444 Thanks to Spredzy for making this PR. This is tracked in jira: https://tickets.puppetlabs.com/browse/MODULES-1982 This pattern has poked up a few differ