On Tue, May 22, 2012 at 11:20 PM, Walter Heck <walterh...@gmail.com> wrote:
> On Tue, May 22, 2012 at 12:02 AM, Marc Zampetti <marc.zampe...@gmail.com> > wrote: > > Is Puppet Labs saying they are ending support of MySQL and instead will > only > > support PostgreSQL? That is going to be a big problems for shops that do > not > > support PostgresSQL, or are only allowed to run DB systems on an approved > > list. Why wouldn't a DB-agnostic model be used? > > > > Right now, I can say that due to these types of issues, I cannot even > > evaluate PuppetDB, and will not be able to for the foreseeable future. > > (cc'd the mysql list as I'm pretty sure the boys over there have some > interest in this) > > As a provider of puppet consulting I can say it will be a harder sell > to clients if we need them to use postgres instead of MySQL in order > to use PuppetDB. It's not impossible of course, but introducing an > additional barrier for puppet will give us additional trouble > convincing our clients :) > I sympathize, and that's why this is an optional component; it's not required in any way for Puppet to function. ActiveRecord-based storeconfigs isn't going away any time soon (and certainly not without more dialogue with the community); it remains an entirely supported option. For customers who feel the improved scalability and performance aren't worth the opportunity cost, they can continue to use the existing storeconfigs backend to which they're accustomed. That remains a fully-supported way to deploy Puppet. > > You mentioned degraded performance, do you have any numbers on what > kind of performance degradation we are talking about? I wouldn't mind > some degraded performance if that means we can keep smaller clients on > MySQL. > > Also, have you looked at MariaDB 5.5? it is a drop-in replacement for > MySQL with much better performance for any query optimiser related > things (which I'm pretty sure the nested joins are also part of). > While we don't have immediate plans to support MySQL or MariaDB ourselves, I would very much encourage others to create such backends for PuppetDB. Our wire formats are documented and versioned, and the PuppetDB terminus code that handles translation from Puppet's data structures into the wire format is 100% reusable to that end. These layers of abstraction were put into place specifically to enable such interoperability and to prevent alternate backends from becoming second-class citizens of the puppet ecosystem. We'd be happy to assist in these endeavors however we can! deepak > > -- > Walter Heck > > -- > Check out my startup: Puppet training and consulting @ > http://www.olindata.com > Follow @olindata on Twitter and/or 'Like' our Facebook page at > http://www.facebook.com/olindata > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@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. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
