From owner-freebsd-current@FreeBSD.ORG Tue Jan 13 21:29:42 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 75C288F4 for ; Tue, 13 Jan 2015 21:29:42 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 44FC8E2F for ; Tue, 13 Jan 2015 21:29:41 +0000 (UTC) Received: from [192.168.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 6AA868EBCE for ; Tue, 13 Jan 2015 21:29:35 +0000 (UTC) Message-ID: <54B58E48.2030107@freebsd.org> Date: Tue, 13 Jan 2015 16:29:44 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Devops question: unattended installs of FreeBSD? References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8Sn2ohsb2LTBSNLMsWdM5gLmePw8d5NDX" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2015 21:29:42 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --8Sn2ohsb2LTBSNLMsWdM5gLmePw8d5NDX Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-01-13 16:10, Craig Rodrigues wrote: > On Mon, Jan 12, 2015 at 12:12 PM, John Nielsen wro= te: >=20 >> >> I'd be happy to provide more specific suggestions if needed. It really= >> depends on how fully automated you want things to be and how much >> customization you want to include, as well as what you have available = in >> the install environment. If you're installing on live VMs then you fir= st >> have to get them booted. A custom ISO or MFS image is probably the sim= plest >> for that, though PXE is also an option. (Actually, serving an mfsBSD i= mage >> via PXE is pretty straightforward.) >> >> > Thanks! You provided some excellent concrete examples for how to do > unattended FreeBSD installs. >=20 > In the past 6 months, I have had two different people ask me how to: > -> create a PXE boot server > -> take the ISO image for FreeBSD 9.2, FreeBSD 10.1, etc. > -> create a kickstart environment where it is possible to PXE boot = a > cluster of machines, and > have an unattended "kickstart" install take place of the variou= s > FreeBSD versions >=20 > I have coded this kind of stuff up myself in the past and written my ow= n > scripts. > However, it would be really nice if we had more straightforward > documentation and example scripts for doing this. > That way, the average devops engineer experienced with Linux and kickst= art > can set this up with no problem, instead of having to struggle and figu= re > things out. >=20 > It looks like all this stuff is possible under FreeBSD. The main probl= em I > see is that the > access to the documentation for doing this is not straightforward at al= l. >=20 > If I do a web search for "Linux kickstart", the search results I get le= ad > me to documentation > that is actually quite good. I am not a Linux expert, but I can read t= hat > stuff and figure out how to set it > up reasonably quickly. >=20 > If I do a web search for "FreeBSD kickstart", the top search results I = get > lead to a few broken > web links, and some private notes from different people on the Internet= =2E > The notes are not bad, > but not as straightforward to follow as the Linux documentation links. >=20 > Since you have some good experience with this, can we create a thread o= n > https://forums.freebsd.org > with the title "FreeBSD kickstart" with some step-by-step examples for > creating a "kickstart" environment? >=20 > That way over time, a web search for "FreeBSD kickstart" will show the > forum post with top-notch examples. >=20 > Thanks. > -- > Craig > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 Martin Matu=9Aka gave a talk at AsiaBSDCon 2014 about using 'Foreman' in addition to Puppet to manage FreeBSD instances. Slides: http://blog.vx.sk/pdf/foreman-asiabsdcon2014.pdf Video: https://www.youtube.com/watch?v=3Dnb8jB5x0OX4 So foreman does the inventory management (for physical hosts etc), and manages network booting mfsBSD and running the scripted installation, and boot strapping puppet, which then takes over the config management side of things. My self, I've looked at using zfs send|receive to deploy new hosts, since I am deploying servers in remote data centers where I don't have another host to PXE Boot off of. --=20 Allan Jude --8Sn2ohsb2LTBSNLMsWdM5gLmePw8d5NDX 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.22 (MingW32) iQIcBAEBAgAGBQJUtY5MAAoJEJrBFpNRJZKfe+YQAKDW2OF9Hr2mKyTA3wDhHP4F A1G8esTGwqhhPm2fxM0pi/NwLL5eIqpNODLDHcKbo44rgwd5214hezORdRNW16DU 7feliQfqasbxbe23UEJSGOaK/FYIWVCRykczwn/oIIEy8RpWVLenVpUm1QUxKNl9 b3F3/Fm/aGu+bzNNUxq0fVR6A8L7fCNnjkx+TfyKAVWC+0jOObv/eRC2kTasNI3V p94Z6XJq1orGr4xbs+2hcfpM/EYL72aMFacYo1XhpYRvjzlkyLytp/Yq5YtPl6q9 KdM74LaA+68KLDnO/YCH1G6z1Gtpzc9ub5/MRYfckqSowr62+9KJfuuvkkZKOY5M uCh0LWULNdsmYDQZVpVmqz858SkGcPOlA/b1Jyn3Y9AvS8jF5qWZIsePho8Tx2kp fz883RAsIPtkpJ57rMMnZUMZKU0eLPthrY5tuvfaSrDOq8GaVHwptRFkF7OZPxc/ chLKfVivRXfqq+D9zvIhbrn6r6e4VhhSBZjynY7SwcbRUZ08eI4n3C/PQqA974ZH CEPlTcxQgAzQMmFEuO/ytc14XFtOp8qOrSrVoRf51eE1kICbJEZd0iys/+5GrS+Z 47No/iau6uFteKBFfJa35QlBxYFc5LSB07Ttlvr0P8F7tN17euIi4fsbwyZqmmgI Mx2LatdUKp2f5/ixnA78 =RMTR -----END PGP SIGNATURE----- --8Sn2ohsb2LTBSNLMsWdM5gLmePw8d5NDX--