Date: Thu, 06 Sep 2012 21:23:40 +0200 From: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> To: stable@freebsd.org Subject: New port: inofficial/deploy-tools Message-ID: <5048F83C.7090300@omnilan.de>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig883B4EECC99E06BB25226BE4 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hello, for people needing to setup various production systems, multiple times for the same basic hardware but for different purposes, and mainly for people installing embedded systems, my collection of scripts/Makefiles named "deploy-tools" may be of interest. It makes use of standard FreeBSD make processes, but modified in a way that you can handle multiple rollouts in parallel, none touching the regular /usr/src /usr/obj trees. You can "menu" driven (by sbin/deploy-manager): - checkout source (svn+cvsup) and auto-apply local patches - build world/kernel - rollout installer-cd image of the customized system with auto-install-script - rollout "firmware" (RAM-root) images - flash card management for installing firmware images / packages The basic idea is to share platform config for various systems not related otherwise. And of course to manage/archive the configs/results. Therefor the configs are organized in projetcs, which basically is nothing more than a distinct directory tree. The deploy-manager can initialize such projects, taking care of all mandatory config files (provided as templates/examples). "deploy-tools" is the aggregation of several scripts/tools/Makefiles I've been using myself for several years. Only very view "make targets" are reachable by menu, but most of the not-reachable-ones are irrelevant for regular usage. Most important part is the "Embedded Systems" management. This emerged from a former project named FlashBSD. Aim was, to shrink a standard FreeBSD system to fit on a 64MB CF-Card, while still providing most of the admin's features like on regular systems (man pages etc). It makes use of standard processes as much as possible (unlike many other milli- micro- nano- projects) and ensures high robustnes for the target installation. Feedback of course is welcome. No man page available but you'll get infos/advices/descriptions during project initialization. ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/deploy-tools-0.9.5.shar.gz Place it into usr/ports/inofficial gunzip and run the shell archive. Then you can install it like every other port. It's not feature complete yet, and may make assumptions not fitting for everybody, but if you're tired manually applying local patches, comparing/copying/merging configurations and doing over and over the same, it may be helpful. Especially if you want to setup any WRAP/NET devices! And also for VMWARE rollouts! You can have a ISO ready for auto-installtion with very view key strokes, idle brain and lots of spare time - depending on your building machine ;-) Only tested on FreeBSD 9, CD-imaging won't work on systems with makefs lacking cd9660 support! -Harry --------------enig883B4EECC99E06BB25226BE4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlBI+DwACgkQLDqVQ9VXb8gOPACeKQJiM5OS+UO5VCP0SB4FyMNK KMEAoKfvlnjzv2lkI/DhBWnDfydKCsmx =AMh3 -----END PGP SIGNATURE----- --------------enig883B4EECC99E06BB25226BE4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5048F83C.7090300>