> Next thing you know we'll need a rules engine and an artificial > intelligence. > > Yeah, we don't want to go there. But multinode deployment? Yes, we > want to go there.
I think that's a great idea in principle, with several potential pitfalls. Do you have specific ideas about what capabilities should be added to Puppet to support it? For instance, are you thinking of a new tool for this, or of adding to puppetd? If a new tool, then how would it interact with puppetd, if at all? > Puppet is a tool, yes, but also think of the greater potential ecosystem. [...] > I think there is room to do more. [...] > puppet > and it's model will be the core around what we'll do. Always. That's encouraging, thanks. I guess part of what I'm trying to grapple with is where some of the new functionality will fit in the Puppet ecosystem. I am undoubtedly also worried about some issues that really are much more Reductive's business than mine, but I care because I love Puppet and I want it to keep working for me. John -- 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.
