On Tue, Mar 16, 2010 at 1:14 PM, David Schmitt <da...@dasz.at> wrote:
> On 3/16/2010 6:13 PM, Joe McDonagh wrote:
>>
>> David Schmitt wrote:
>>>
>>>
>>>
>>> Which leads me to another idea: inter-node dependencies:
>>>
>>> | node a { mysql_db { "foo": ... } }
>>> |
>>> | node b { app { "x": after => A>>Mysql_db["foo"]; } }
>>>
>>>
>>>
>> David, are you suggesting this, or are you saying that this works?
>>
>
> I'm suggesting something like this. Internally it'd probably work like
> external_resource (see -dev list for details) but would query the
> storeconfig DB instead of calling a script on the client.
>
>Yeah I had the same idea. I think Luke was suggesting a higher level of modelling, but that can work now, provided there's a way to easily create the content for the remote resource check. The Func-like approach would be for each node to surface what it's "gates" were, and then set up authorization to allow other nodes to ask them if a particular task was performed. I'm not /quite/ sure that is sufficient though, or otherwise the gates would have to be pretty smart -- for controlling an app upgrade you would need more of a check than just seeing if the DB was present or a version number was in a table. --Michael -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
