Well I should have mentioned that the ESXi is also running a Windows server VM for a custom app that requires it. So the idea was to have one box running ESXi and reduce hardware costs.
--- On Thu, 5/21/09, Jason Dixon <ja...@dixongroup.net> wrote: > From: Jason Dixon <ja...@dixongroup.net> > Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 > To: "Obiozor Okeke" <obiozorok...@yahoo.com> > Cc: misc@openbsd.org, "Diana Eichert" <deich...@wrench.com> > Date: Thursday, May 21, 2009, 7:19 AM > On Thu, May 21, 2009 at 06:47:08AM > -0700, Obiozor Okeke wrote: > > Hi Diana (and Stuart) thanks for all your advice. > > > > The problem or nut we're > > trying to crack is that we're trying to deploy OpenBSD > to remote clients and > > we wanted an inexpensive but very high reliability > system with the flexibility > > to change configurations (switch in/out different VMs) > and add/modify services > > remotely on-the-fly. For example we could > upgrade a client from 4.4 to 4.5 > > along with all the custom apps and client data > packaged in a VM. We would > > grab the old 4.4 VM bring it back to our lab, then > upgrade and re-configure it > > the way we wanted to and drop it back on the > ESXi. Then just change the > > network configs and switch the old for the new all > remotely without ever > > visiting the client > > No offense, but that's a terrible design. Get > yourself two inexpensive > systems (5501's are ok) and run them in a failover > configuration. You > have redundancy and the flexiblity to alternate between > releases. > Without the headache of middleware patches, an unsupported > configuration, etc. > > -- > Jason Dixon > DixonGroup Consulting > http://www.dixongroup.net/
