git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: John Keeping <john@keeping.me.uk>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: offtopic: ppg design decisions - encapsulation
Date: Tue, 7 May 2013 10:32:15 -0400	[thread overview]
Message-ID: <CACPiFCLtYKsXQ-aoPadJxkB5phQ+j2PAfHnDTJK6B85mcfRF_g@mail.gmail.com> (raw)
In-Reply-To: <20130506155353.GF25912@serenity.lan>

On Mon, May 6, 2013 at 11:53 AM, John Keeping <john@keeping.me.uk> 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@gmail.com
 -  ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 ~ http://docs.moodle.org/en/User:Martin_Langhoff

      reply	other threads:[~2013-05-07 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 15:34 offtopic: ppg design decisions - encapsulation Martin Langhoff
2013-05-06 15:53 ` John Keeping
2013-05-07 14:32   ` Martin Langhoff [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACPiFCLtYKsXQ-aoPadJxkB5phQ+j2PAfHnDTJK6B85mcfRF_g@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=john@keeping.me.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).