From: Nick <oinksocket@letterboxes.org>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Elia Pinto <gitter.spiros@gmail.com>,
David Aguilar <davvid@gmail.com>,
"Randal L. Schwartz" <merlyn@stonehenge.com>,
Darek Bridges <darek.bridges@me.com>,
git@vger.kernel.org
Subject: Re: git with large files...
Date: Sat, 21 Jul 2012 22:04:52 +0100 [thread overview]
Message-ID: <500B1974.5070508@letterboxes.org> (raw)
In-Reply-To: <CACPiFCLTPi5i3RZHwOD-+OJ_zSbtOwe7VLy=NMO1MUKPVyPHEw@mail.gmail.com>
On 21/07/12 15:42, Martin Langhoff wrote:
> On Sat, Jul 21, 2012 at 3:11 AM, Elia Pinto <gitter.spiros@gmail.com> wrote:
>> Well, many folks use puppet in serverless configuration pushing the
>> manifest from a central git server via cron and applying locally the
>> configuration fetched. In this sense git IS used for deployement. And,
>> for a configuration management system as puppet this could be a
>> sensible thing to do - reduce load, scalability ecc.
>
> That's a great thing to know, and timely too. I am looking at Puppet,
> and worried a bit about reported memory load on the server side (and
> some rumours of memory footprint issues on the client side too).
>
> Can you point me to more information & discussion?
We use "masterless" puppet, deployed using gitolite post-receive hooks. The
most useful clues I found are here.
http://groups.google.com/group/puppet-users/browse_thread/thread/ed9a4032b31bd8d4/e1a68aa8ea91305d
http://semicomplete.com/presentations/puppet-at-loggly/puppet-at-loggly.pdf.html
http://current.workingdirectory.net/posts/2011/puppet-without-masters/
http://bitfieldconsulting.com/scaling-puppet-with-distributed-version-control
We had to join the dots ourselves. Works for us so far, but it's only about six
months old. We don't have lots of servers or very exacting requirements, just a
inclination against the pull orthodoxy and the freedom to experiment. Can't
comment about memory footprint, except it's not been a problem for us. (On the
other hand I am not that enamoured with Puppet's DSL design, I might prefer to
avoid it if I could.)
N
next prev parent reply other threads:[~2012-07-21 21:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 16:27 git with large files Darek Bridges
2012-07-20 22:54 ` Randal L. Schwartz
2012-07-20 23:28 ` Martin Langhoff
2012-07-21 3:47 ` David Aguilar
2012-07-21 7:11 ` Elia Pinto
2012-07-21 14:42 ` Martin Langhoff
2012-07-21 15:53 ` Elia Pinto
2012-07-22 6:48 ` Elia Pinto
2012-07-22 9:37 ` Kalle Launiala
2012-07-21 21:04 ` Nick [this message]
2012-07-21 14:40 ` Martin Langhoff
2012-07-22 20:54 ` Junio C Hamano
2012-07-23 4:23 ` Sitaram Chamarty
2012-07-23 7:23 ` Kalle Launiala
2012-07-29 18:47 ` Drew Northup
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=500B1974.5070508@letterboxes.org \
--to=oinksocket@letterboxes.org \
--cc=darek.bridges@me.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@gmail.com \
--cc=martin.langhoff@gmail.com \
--cc=merlyn@stonehenge.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).