Agreed. On Thu, Jan 22, 2009 at 11:35 PM, [email protected] < [email protected]> wrote:
> > I'm not suggesting we use Puppet instead of Scalr. > > I'm suggesting that Scalr use puppet for its scripting engine - to > customize the images. Right now Scalr uses its own scripting stuff. > Why not use puppet? > > The problem with just modifying the images is that you don't have a > way to reproduce them, version them, etc. Also, puppet allows for > much more dynamic behavior in instances than is likely possible to > build yourself. > > So, there is an overwhelming use case for puppet in this case. > > On Jan 22, 3:04 pm, Frédéric Sidler <[email protected]> wrote: > > I would say that puppet is a great tool, but scalr simplifies a > > multimachines configuration by synchronizing all of the for you in a real > > easy way. Regarding a regular web app for example, you just adapt the app > > role, www, memcache and mysql can stay the same. So modifying the app > role > > and being able to replicate this modification thank to "synchronize all" > > will let you propagate your modifications across all running app roles > and > > bundle your image to be stored on S3 in case of additionnal need. > > > > I'm pretty sure there could be a need for puppet, but not for this use > case, > > I think. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
