On Mon, May 6, 2013 at 11:53 AM, John Keeping <john@xxxxxxxxxxxxx> wrote: > I'm not sure I fully understand what the reports are, but it sounds like > they are closely related to original configuration commits. If that is > the case, have you considered using Git notes instead of a separate > repository? Interesting suggestion! I read up on git-notes. Yes, reports are closely related to a commit -- it's a lot of the execution of puppet with that config on a client node. At the same time, we have one report per change deployment, per client -- with thousands of clients. So it will be a large dataset, and a transient one -- I intend to use git as a store-and-forward mechanism for the reports, and it is safe&sane to forget old reports. I don't see much ease-of-expiry in the notes, so I guess I would have to write that myself, which complicates things a bit :-) cheers, m -- martin.langhoff@xxxxxxxxx - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs.moodle.org/en/User:Martin_Langhoff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html