<p>None of which is a reason to avoid Puppet. It is a good way of doing push. Actually, the two can work well together. Keeping your Puppet configs in a local Git repository is a Good Idea™.</p>
<div class="gmail_quote">On Aug 8, 2011 5:35 PM, "Jim Kinney" <<a href="mailto:jim.kinney@gmail.com">jim.kinney@gmail.com</a>> wrote:<br type="attribution">> With configs in version control it easy to roll back from a mistake.<br>
> Pushing from central repo is required for fast config change : for servname<br>> in $list do pushconfig&rehup; done<br>> For pull, each must have a key on central or use same key (BAD!). Push just<br>> needs central key installed by default.<br>
> Other reasons to complicated for thumb typing on cell :-)<br>> On Aug 8, 2011 3:49 PM, "Wolf Halton" <<a href="mailto:wolf.halton@gmail.com">wolf.halton@gmail.com</a>> wrote:<br>>> Jim..<br>>><br>
>> I am almost sure that a pull from the clients makes more sense than a<br>> push,<br>>> but as usual I am open to suggestions.<br>>> Why put the config files into a git or svn repo? Why not serve them<br>
> directly<br>>> fro the actual files. I have been reading about puppet for a couple of<br>>> hours and sorting out what would be useful here. It seems hugely useful,<br>>> especially if I am pushing out configurations on a larger scale than I<br>
>> currently am doing.<br>>><br>>> I have a test script that uses rsync to pull the files off the server, now<br>>> that I am using crontab better, I can use cron to set the script to run<br>> once<br>
>> an hour. I could use puppet to call the cron job that runs that on the<br>>> client side, but rsync requires ssh password for the user. I do not<br>>> understand how to set up puppet to pull the file-structure directly, but I<br>
>> think it would mean I didn't need the rsync script or the cron job, which<br>>> would save a lot of lash-up, and wouldn't have to use an rsync daemon on<br>> the<br>>> server.<br>>><br>
>> -Wolf<br>>><br>>> On Thu, Aug 4, 2011 at 2:30 PM, Jim Kinney <<a href="mailto:jim.kinney@gmail.com">jim.kinney@gmail.com</a>> wrote:<br>>><br>>>> I would look at putting the config files in a subversion or git repo and<br>
>>> pushing out with repo sync or rsync or using puppet or cfengine to handle<br>>>> this.<br>>>> On Aug 4, 2011 1:49 PM, "Wolf Halton" <<a href="mailto:wolf.halton@gmail.com">wolf.halton@gmail.com</a>> wrote:<br>
>>> > Oh, ok.. Thanks,<br>>>> > I have not used automount before. Would you feel safe mounting a<br>> critical<br>>>> > directory with it - not necessarily a remote /home directory?<br>
>>> > The nfs share I have up is holding the config files for a web app. This<br>>>> was<br>>>> > our solution to having to update the config files on several servers in<br>>>> the<br>
>>> > event that they needed to be edited. Without it, my test box has a copy<br>>>> of<br>>>> > the source on it, but it is plain that this failsafe didn't work all<br>> that<br>>>> > well.<br>
>>> ><br>>>> > On Thu, Aug 4, 2011 at 12:57 PM, Lightner, Jeff <<a href="mailto:JLightner@water.com">JLightner@water.com</a>><br>>>> wrote:<br>>>> ><br>>>> >> Right – Avery’s email was saying you could use automount rather than<br>
>>> >> fstab. With automount the filesystem doesn’t mount at boot time but<br>> does<br>>>> >> mount the first time something tries to use it which should be long<br>>>> after<br>
>>> >> boot.****<br>>>> >><br>>>> >> ** **<br>>>> >><br>>>> >> Automount also means the filesystem gets unmounted automatically when<br>>>> not<br>
>>> >> in use and remounted when used later. One nice side to this is that if<br>>>> the<br>>>> >> exporting server goes down and it isn’t currently NFS mounted on your<br>>>> server<br>
>>> >> it doesn’t cause problems like hard NFS mounts do. ****<br>>>> >><br>>>> >> ** **<br>>>> >> ------------------------------<br>>>> >><br>>>> >> *From:* <a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a> [mailto:<a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a>] *On Behalf Of<br>
>>> *Wolf<br>>>> >> Halton<br>>>> >> *Sent:* Thursday, August 04, 2011 12:23 PM<br>>>> >> *To:* Atlanta Linux Enthusiasts<br>>>> >><br>>>> >> *Subject:* Re: [ale] Fstab fails<br>
>>> >> ****<br>>>> >><br>>>> >> ** **<br>>>> >><br>>>> >> In my case, the system is coming up but just without the nfs directory<br>>>> >> mounted. ****<br>
>>> >><br>>>> >> On Aug 4, 2011 9:03 AM, "Lightner, Jeff" <<a href="mailto:JLightner@water.com">JLightner@water.com</a>> wrote:<br>>>> >> > Good idea.<br>>>> >> ><br>
>>> >> ><br>>>> >> ><br>>>> >> ><br>>>> >> ><br>>>> >> ><br>>>> >> > ________________________________<br>>>> >> > From: <a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a> [mailto:<a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a>] On Behalf Of<br>
>>> >> Avery Ceo<br>>>> >> > Sent: Wednesday, August 03, 2011 7:42 PM<br>>>> >> > To: Atlanta Linux Enthusiasts; <a href="mailto:transam@verysecurelinux.com">transam@verysecurelinux.com</a><br>
>>> >> > Subject: Re: [ale] Fstab fails<br>>>> >> ><br>>>> >> ><br>>>> >> > Have you considered the automounter? By waiting until the first<br>>>> attempt<br>
>>> >> to read a file before mounting the share, you might avoid your startup<br>>>> >> issue, and you would get remounts after a lost connection for free if<br>>>> there<br>>>> >> is a network blip.<br>
>>> >> > On Aug 3, 2011 6:47 PM, "Bob Toxen" <<a href="mailto:transam@verysecurelinux.com">transam@verysecurelinux.com</a><br>>>> <mailto:<br>>>> >> <a href="mailto:transam@verysecurelinux.com">transam@verysecurelinux.com</a>>> wrote:<br>
>>> >> >> This still will hang in startup (though you'll probably be in<br>>>> >> >> multiuser).<br>>>> >> >><br>>>> >> >> Specify timeouts in case NFS cannot start, e.g., the server is<br>
> down.<br>>>> >> >><br>>>> >> >> Bob Toxen<br>>>> >> >><br>>>> >> >> On Wed, Aug 03, 2011 at 04:21:47PM -0400, Andrew Wade wrote:<br>
>>> >> >>> With NFS, I set fstab<br>>>> >> >>><br>>>> >> >>> server:/ifs/fs02 /ifs/fs02 nfs bg,noauto,rsize=8192,wsize=8192 0 0<br>>>> >> >>><br>
>>> >> >>> *note the noauto, this tells it to not automount. If it tries to<br>>>> >> automount<br>>>> >> >>> and is unable, your server will stall in startup. So you put this<br>
>>> entry<br>>>> >> in<br>>>> >> >>> /etc/rc.local:<br>>>> >> >>><br>>>> >> >>> mount /ifs/fs02<br>>>> >> >>><br>
>>> >> >>> Also check to make sure that nfs and portmap services are started<br>>>> upon<br>>>> >> boot<br>>>> >> >>> time.<br>>>> >> >>><br>
>>> >> >>> That way, the server starts up and then mounts the nfs under<br>>>> rc.local<br>>>> >> (where<br>>>> >> >>> if the nfs share hangs, it would not affect the normal system<br>
>>> startup).<br>>>> >> >>><br>>>> >> >>><br>>>> >> >>><br>>>> >> >>> Andrew<br>>>> >> >>> RHCE<br>
>>> >> >>><br>>>> >> >>> On Tue, Aug 2, 2011 at 5:50 PM, planas <<a href="mailto:jslozier@gmail.com">jslozier@gmail.com</a><mailto:<br>>>> >> <a href="mailto:jslozier@gmail.com">jslozier@gmail.com</a>>> wrote:<br>
>>> >> >>><br>>>> >> >>> > **<br>>>> >> >>> > Wolf<br>>>> >> >>> ><br>>>> >> >>> > Could configuration be faulty, I asked about setting an internal<br>
>>> ntfs<br>>>> >> drive<br>>>> >> >>> > awhile ago and I got this link from Ubuntu:<br>>>> >> >>> ><br>>>> >> >>> > <a href="https://help.ubuntu.com/community/Fstab">https://help.ubuntu.com/community/Fstab</a><br>
>>> >> >>> ><br>>>> >> >>> > It has links to more network configuration.<br>>>> >> >>> ><br>>>> >> >>> ><br>>>> >> >>> > On Tue, 2011-08-02 at 14:27 -0400, Wolf Halton wrote:<br>
>>> >> >>> ><br>>>> >> >>> > Can you think of any reason why fstab would not be read on<br>> reboot.<br>>>> >> Ubuntu<br>>>> >> >>> > lucid have an nfs share that was not mounted automagically when<br>
> I<br>>>> >> rebooted<br>>>> >> >>> > the client machine. Broke a bunch of stuff.<br>>>> >> >>> > Wolf<br>>>> >> >>> > PS mount -a picked up and mounted the nfs directory.<br>
>>> >> >>> ><br>>>> >> >>> > _______________________________________________<br>>>> >> >>> > Ale mailing list<br>>>> >> >>> > Ale@ale.orghttp://<a href="http://mail.ale.org/mailman/listinfo/ale">mail.ale.org/mailman/listinfo/ale</a><<br>
>>> >> <a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a>><br>>>> >> >>> > See JOBS, ANNOUNCE and SCHOOLS lists athttp://<br>>>> >> <a href="http://mail.ale.org/mailman/listinfo">mail.ale.org/mailman/listinfo</a><<a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a>><br>
>>> >> >>> ><br>>>> >> >>> ><br>>>> >> >>> ><br>>>> >> >>> > --<br>>>> >> >>> > Jay Lozier<br>
>>> >> >>> > <a href="mailto:jslozier@gmail.com">jslozier@gmail.com</a><mailto:<a href="mailto:jslozier@gmail.com">jslozier@gmail.com</a>><br>>>> >> >>> ><br>>>> >> >>> > _______________________________________________<br>
>>> >> >>> > Ale mailing list<br>>>> >> >>> > <a href="mailto:Ale@ale.org">Ale@ale.org</a><mailto:<a href="mailto:Ale@ale.org">Ale@ale.org</a>><br>>>> >> >>> > <a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a><br>
>>> >> >>> > See JOBS, ANNOUNCE and SCHOOLS lists at<br>>>> >> >>> > <a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a><br>>>> >> >>> ><br>
>>> >> >>> ><br>>>> >> >><br>>>> >> >>> _______________________________________________<br>>>> >> >>> Ale mailing list<br>>>> >> >>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><mailto:<a href="mailto:Ale@ale.org">Ale@ale.org</a>><br>
>>> >> >>> <a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a><br>>>> >> >>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>>>> >> >>> <a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a><br>
>>> >> >><br>>>> >> >> _______________________________________________<br>>>> >> >> Ale mailing list<br>>>> >> >> <a href="mailto:Ale@ale.org">Ale@ale.org</a><mailto:<a href="mailto:Ale@ale.org">Ale@ale.org</a>><br>
>>> >> >> <a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a><br>>>> >> >> See JOBS, ANNOUNCE and SCHOOLS lists at<br>>>> >> >> <a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a><br>
>>> >> ><br>>>> >> ><br>>>> >> ><br>>>> >> ><br>>>> >> ><br>>>> >> ><br>>>> >> > Proud partner. Susan G. Komen for the Cure.<br>
>>> >> ><br>>>> >> > Please consider our environment before printing this e-mail or<br>>>> >> attachments.<br>>>> >> > ----------------------------------<br>
>>> >> > CONFIDENTIALITY NOTICE: This e-mail may contain privileged or<br>>>> >> confidential information and is for the sole use of the intended<br>>>> >> recipient(s). If you are not the intended recipient, any disclosure,<br>
>>> >> copying, distribution, or use of the contents of this information is<br>>>> >> prohibited and may be unlawful. If you have received this electronic<br>>>> >> transmission in error, please reply immediately to the sender that you<br>
>>> have<br>>>> >> received the message in error, and delete it. Thank you.<br>>>> >> > ----------------------------------<br>>>> >> ><br>>>> >> > ****<br>
>>> >><br>>>> >> _______________________________________________<br>>>> >> Ale mailing list<br>>>> >> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>>>> >> <a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a><br>
>>> >> See JOBS, ANNOUNCE and SCHOOLS lists at<br>>>> >> <a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a><br>>>> >><br>>>> >><br>
>>> ><br>>>> ><br>>>> > --<br>>>> > This Apt Has Super Cow Powers - <a href="http://sourcefreedom.com">http://sourcefreedom.com</a><br>>>><br>>>> _______________________________________________<br>
>>> Ale mailing list<br>>>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>>>> <a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a><br>>>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>>> <a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a><br>>>><br>>>><br>>><br>>><br>>> --<br>>> This Apt Has Super Cow Powers - <a href="http://sourcefreedom.com">http://sourcefreedom.com</a><br>
</div>