Hi, thanks to virtualization, my fleet of FreeBSD hosts have grown to more than dozen, and it still grows. There are some files that need to be identical on all of them (aliases, sudoers, root crontab, pkg repo files etc.). I was looking at puppet and cfengine but learning and implementing those seem like an overkill for my purpose. Are there any other elegant solutions which can help me achieve my goal? Thank you in advance, -- Marko Cupa? https://www.mimar.rs
On Thu, 05 Feb 2015 13:02:34 +0100, Marko Cupa? <marko.cupac at mimar.rs> wrote:> Hi, > > thanks to virtualization, my fleet of FreeBSD hosts have grown to more > than dozen, and it still grows. There are some files that need to be > identical on all of them (aliases, sudoers, root crontab, pkg repo > files etc.). > > I was looking at puppet and cfengine but learning and implementing those > seem like an overkill for my purpose. > > Are there any other elegant solutions which can help me achieve my goal? > > Thank you in advance,Cron and rsync. Or create a pkg which you install on all servers. Just some quick ideas. In the end you just want to use something like puppet. :-) Ronald.
> On Feb 5, 2015, at 7:02 AM, Marko Cupa? <marko.cupac at mimar.rs> wrote: > > Hi, > > thanks to virtualization, my fleet of FreeBSD hosts have grown to more > than dozen, and it still grows. There are some files that need to be > identical on all of them (aliases, sudoers, root crontab, pkg repo > files etc.). > > I was looking at puppet and cfengine but learning and implementing those > seem like an overkill for my purpose. > > Are there any other elegant solutions which can help me achieve my goal? > > Thank you in advance,Marko We use a mix of two tools Radmind http://webservices.itcs.umich.edu/mediawiki/radmind/index.php/Main_Page Radmind is a toll well suited for tracking changes in static configs and fairly well at tracking and reverting changes on a entire working system . While it was targeted at OS X originally we have used it on FreeBSD , centos , then, fedora , and Solaris . Also we use ansibel . Ansibel is a agent less config and system management toll written in Python . It only requires Python 24 and ssh on the target hosts . It's flexible and relatively easy compared to some other tools . It's also well supported on rhel/ centos and FreeBSD . http://www.ansible.com/home Lastly you can always use entr and rsync https://bitbucket.org/eradman/entr it's in ports too --- Mark saad | mark.saad at longcount.org> -- > Marko Cupa? > https://www.mimar.rs > _______________________________________________ > freebsd-stable at freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
On Thu, 5 Feb 2015 13:02:34 +0100 Marko Cupa? <marko.cupac at mimar.rs> wrote:> Hi, > > thanks to virtualization, my fleet of FreeBSD hosts have grown to more > than dozen, and it still grows. There are some files that need to be > identical on all of them (aliases, sudoers, root crontab, pkg repo > files etc.). > > I was looking at puppet and cfengine but learning and implementing those > seem like an overkill for my purpose. > > Are there any other elegant solutions which can help me achieve my goal? > > Thank you in advance,If they really need to be identical all the time, I'd put them on a network share mounted at boot and symlink on them from etc, var/mail, and so on. repositories can be mount points themselves, so clearly candidates for a network share, too. Alonso -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 603 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20150205/75c31cc5/attachment.sig>
Hello, I am not sure about whole Freebsd system, but as for software deploying and development try the "docker" software. https://www.docker.com/whatisdocker/ 05.02.2015 14:02, Marko Cupa? ?????:> Hi, > > thanks to virtualization, my fleet of FreeBSD hosts have grown to more > than dozen, and it still grows. There are some files that need to be > identical on all of them (aliases, sudoers, root crontab, pkg repo > files etc.). > > I was looking at puppet and cfengine but learning and implementing those > seem like an overkill for my purpose. > > Are there any other elegant solutions which can help me achieve my goal? > > Thank you in advance,-- Regards, Oleksii Zolotarov
On Thu, Feb 5, 2015 at 6:02 AM, Marko Cupa? <marko.cupac at mimar.rs> wrote:> Hi, > > thanks to virtualization, my fleet of FreeBSD hosts have grown to more > than dozen, and it still grows. There are some files that need to be > identical on all of them (aliases, sudoers, root crontab, pkg repo > files etc.). > > I was looking at puppet and cfengine but learning and implementing those > seem like an overkill for my purpose. >Speaking strictly of puppet, I don't see how it's overkill if it's still growing. Are there any other elegant solutions which can help me achieve my goal?>pdsh, NFS -- Adam
> I was looking at puppet and cfengine but learning and implementing those > seem like an overkill for my purpose. > > Are there any other elegant solutions which can help me achieve my goal?rdist. It used to be in the base system, but was moved to ports for specious security paranoia reasons. Set the appropriate environment variable to have it use ssh(1) instead of rsh(1) and you're good to go. --lyndon
Hi, On Thu, 5 Feb 2015 13:02:34 +0100 Marko Cupa? <marko.cupac at mimar.rs> wrote:> thanks to virtualization, my fleet of FreeBSD hosts have grown to more > than dozen, and it still grows. There are some files that need to be > identical on all of them (aliases, sudoers, root crontab, pkg repo > files etc.). > > I was looking at puppet and cfengine but learning and implementing > those seem like an overkill for my purpose. > > Are there any other elegant solutions which can help me achieve my > goal? >I started a long time ago with scripts doing this job. It has one clear advantage which is also its biggest disadvantage. Your scripts do precisely what you want but it is you who has to keep up with the herd. I got later caught in other work when I started to enable them to do even customised configuration. Erich