Date: Thu, 7 May 2009 08:01:57 -0400 From: Bill Moran <wmoran@potentialtech.com> To: Warren Guy <warren.guy@calorieking.com> Cc: freebsd-questions@freebsd.org Subject: Re: Developing and maintaining a rapidly deployable image of an installed system Message-ID: <20090507080157.93c8e5ee.wmoran@potentialtech.com> In-Reply-To: <4A025F42.50308@calorieking.com> References: <4A025F42.50308@calorieking.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warren Guy <warren.guy@calorieking.com> wrote: > > Hi everyone, > > I'm just wondering if there is an established best practice for > developing and maintaining a rapidly deployable image of an installed > FreeBSD system? > > If anyone can point me towards documentation or any other resources that > might be of use I would greatly appreciate it. One of the tools we've been using extensively is FreeBSD's jail system. Especially with the ezjail port, it's pretty easy to have a backup tarball of each "system" that can then be easily deployed to another server if needed. It also makes it easy to migrate "servers" to other hardware in order to do upgrades, or re-balance workload if one particular piece of hardware is getting over or under utilized. The host system is a very basic install -- mostly just give it an IP and add users for the administrators. All the ports and details of their configs are in the individual jails. It's much more efficient than using something like VMware, which has horrific performance penalties. -- Bill Moran http://www.potentialtech.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090507080157.93c8e5ee.wmoran>