On Friday, December 09, 2011 04:45:05 PM Pandu Poluan wrote: > On Dec 9, 2011 2:18 PM, "J. Roeleveld" <jo...@antarean.org> wrote: > > On Thu, December 8, 2011 5:01 pm, Pandu Poluan wrote: > > > On Dec 8, 2011 9:46 PM, "Jarry" <mr.ja...@gmail.com> wrote: > > >> This server is ~50 miles away, and if I screw something > > >> and it does not boot up, I will have to go there and fix it > > >> on place. One small typo in ~50 config-files which must be > > >> updated is just enough to cause it... > > > > > > That's why I no longer deploy baremetal servers these days. Always > > > as a VM > > > on top of a hypervisor, with a small VM dedicated as an SSH tunnel. > > > If I mess up, I can use the hypervisor management tool to reboot > > > the VM, or open > > > a console session, or even revert to a "known good" state. > > > > A seperate machine with serial-console or Ethernet-KVM on the mainboard > > also helps. Especially when updating the host :) > > > > My new servers will all have Ethernet-KVM for this reason. > > How I wish I can deploy an Ethernet KVM... my boss thought it was a good > idea, until he saw the price tag :-/ > > Rgds,
My new server has one on the mainboard (Tyan S5512GM4NR) that has a web- interface from which I can start a java-app for remote desktop. Other options: reset/power control, online read-out of sensor-data and I can patch the BIOS without starting the server. First time I got this and I like it enough to want it for future servers. -- Joost
