[rancid] Re: Leveraging rancid framework for unix

[Lance]

Sam,

You could always use Ed Ravins wrapper script to most things.
I have only used it to scrap configs not change configs.

At works sam you migt want to check out NDCC. They claim to work with
unix/linux...not sure if it is just config collection or what.

-lance

> -------- Original Message --------
> Subject: [rancid] Re: Leveraging rancid framework for unix
> From: Chris Moody <cmoody at qualcomm.com>
> Date: Mon, January 14, 2008 12:36 pm
> To: smunzani at comcast.net
> Cc: rancid-discuss at shrubbery.net
> Just a thought, but why not have the systems scp/wget down their new
> config(s) from a central location.
> That way you would only need to do something like this:
> ---
> for i in `cat serverlist`; do for x in `cat files-to-copy`; do ssh
> user@$i "wget http://fileserver/$x ." ; done
> Cheers,
> -Chris
> Sam Munzani wrote:
> > Aaron,
> >
> > The goal is not to just run one line command but feed a command-list
> > file like we typically do on rancid. An example below of my command list.
> >
> > sed -e 's/x.x.x.x/y.y.y.y/g' srcfile1 > tmpfile
> > mv tmpfile srcfile1
> > sed -e 's/snmp-community/xyz/g' srcfile2 > tmpfile
> > mv tmpfile srcfile2
> >
> > There are many commands like that. In short, I need to mass change snmp
> > agent configuration file on all servers with new trap destination, new
> > snmp string etc. This is just an example but the changes I need takes
> > roughly 18 commands. If this could be achieved by the ssh syntax you
> > suggested, I am all up for that.
> >
> > Thanks,
> > sam
> >> On Mon, 2008-01-14 at 12:54 -0600, Sam Munzani wrote:
> >>
> >>> Hi,
> >>>
> >>> Did anybody ever explored leveraging rancid frame work for unix login
> >>> and mass changes? I have a need to make edit some files on 200+ servers.
> >>> I was thinking to take F5 rancid files, hack it a bit(to do sudo instead
> >>> of cisco enable) and share with a team. However if somebody already
> >>> worked on this aspect, why reinvent the wheel? I can carry forward and
> >>> tune(if any required) and share with the team.
> >>>
> >>
> >> How about "for a in $LIST; do ssh $a $CMD; done"?  I think trying to use
> >> rancid might be reinventing the wheel for something SSH might already be
> >> capable of doing.
> >>
> >>
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Rancid-discuss mailing list
> > Rancid-discuss at shrubbery.net
> > http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss at shrubbery.net
> http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss