On Jul 15, 2010, at 7:01 AM, R.I.Pienaar wrote:
----- "Brice Figureau" <[email protected]> wrote:
On 15/07/10 15:12, R.I.Pienaar wrote:
----- "R.I.Pienaar" <[email protected]> wrote:
I'll give a quick overview of what I want to build so you can
understand the scope of my question. I essentially want to use a
document database to store facts, classes list and some other
information and then make that availble to puppet in a query
system.
just as an fyi, using a document db - mongo here - running in a
virtual machine on a single AMD 5600+ with 384 ram I am seeing full
update times for all facts, classes and list of agents in these kinds
of times:
Updated data for host nephilim.ml.org with id
4c3f0278241239024c000009 in 0.0240168571472168 seconds
query times is also extremely low, so using this kind of approach
over stored confs has a lot of good things performance wise and
should
scale better than mysql+activerecord
Storeconfigs is slow because it stores _all_ resources and _all_
parameters of every resources, which your system is not doing
(because
you don't need it). It is also slow because it re-reads all this
information to perform the diff with the currently compiled catalog.
That's why we added thin storeconfigs that only persists exported
resources and facts.
Now, I do agree, the storeconfigs deeply needs a refactoring and the
possibility to use different back-ends, and your system might be a
good way toward this direction.
I am not trying to improve store configs at all. I am trying to
make something complete different that serves a different purpose -
one that I think is lacking at the moment. It's more in line with
the old query ability of iClassify, the query system in foreman and
how Chef deals with its couchdb. It's an entirely different approach.
Store configs just wont work for me - masters distributed in
different continents, machines hitting any one of those, networks
often down between them etc.
Don't you have the same problem with your mongo db?
That is, isn't this a relatively intractable problem when using
databases, and any solution used to mitigate it could also be used for
storeconfigs?
I'm a little bit more worried about your query syntax, though :-)
I suspect expending the collection syntax we have in the Puppet DSL
would be preferrable.
yeah, if i wanted to replace stored confs I'd agree. I am not
though, I am writing something to query a document database its not
a resource level abstraction.
--
An ounce of action is worth a ton of theory. --Friedrich Engels
---------------------------------------------------------------------
Luke Kanies -|- http://puppetlabs.com -|- +1(615)594-8199
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" 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/puppet-dev?hl=en.
