kc7...@gmail.com (Patrick) writes: > On May 14, 2011, at 12:55 AM, Simon J Mudd wrote:
... > > Not if they are part of the primary key. That's part of the point. > > Any modern database can sustain thousands of queries a second doing this. > > However, you are right small sites may not want to go this way to > > start with unless configuration using a database is trivial. > > As a side note, putting the information in a csv file should make it > much easier to version along with the rest of your files. I assume, > though I could easily be wrong, that most DBs aren't easy to version > control using GIT and Subversion. Using GIT or subversion, no. But versioning the configuration in the database is hardly difficult to do. (If you got that far you have enough infrastructure and expertise to solve this). > That means (using csv files) you can keep your data in lockstep with > the version of the config files. Indeed and I think that's nice. So the only time this becomes an issue is when the load on the puppet master to provide the lookup based on the extlookup() calls is sufficiently high to be a problem. When it's a problem you override the "csv" lookup to work the same based on some sort of "db lookup" alternative. Simon -- 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.
