git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elia Pinto <gitter.spiros@gmail.com>
To: Martin Langhoff <martin.langhoff@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: Sun, 22 Jul 2012 08:48:50 +0200	[thread overview]
Message-ID: <CA+EOSBm2o+9j0Ykpe01tQmTGApZeJA36mJ=Kt8bNAywfpbODPw@mail.gmail.com> (raw)
In-Reply-To: <CA+EOSBkVh-PvASXf5NOOW40MWzt4gdBm-21ER1EbUWLkCJ3cCA@mail.gmail.com>

I forgot to tell that using git for deploying puppet have also some
disadvantages : you cant'use some puppet feature as external node
classifiers or stored configurations. As always, there are tradeoff.
For more

http: //bitfieldconsulting.com/scaling-puppet-with-distributed-version-control
(the missing link)

cheers


2012/7/21, Elia Pinto <gitter.spiros@gmail.com>:
> Sure . There is a complete paragraph " creating decentralized puppet
> architecture" in "puppet 2.7 cookbook". I am also sure to have read
> the same topic on web on the site bitfieldconsulting.com  , not
> casually : the book's author have his blog there. Sorry i have not the
> complete url now - old smartphone, no wifi etc. But i hope this can
> help you the  same.
>
> Best regards
>
> 2012/7/21, Martin Langhoff <martin.langhoff@gmail.com>:
>> 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?
>>
>> thanks!
>>
>>
>>
>> m
>> --
>>  martin.langhoff@gmail.com
>>  martin@laptop.org -- Software Architect - OLPC
>>  - ask interesting questions
>>  - don't get distracted with shiny stuff  - working code first
>>  - http://wiki.laptop.org/go/User:Martinlanghoff
>>
>
> --
> Inviato dal mio dispositivo mobile
>

-- 
Inviato dal mio dispositivo mobile

  reply	other threads:[~2012-07-22  6:49 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 [this message]
2012-07-22  9:37               ` Kalle Launiala
2012-07-21 21:04           ` Nick
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='CA+EOSBm2o+9j0Ykpe01tQmTGApZeJA36mJ=Kt8bNAywfpbODPw@mail.gmail.com' \
    --to=gitter.spiros@gmail.com \
    --cc=darek.bridges@me.com \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --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).