*Disclaimer I work for a Xsigo Partner, but I also think it is cool stuff. I do not get any compensation from any vendor for any blog post. My opinions are my own, unless I am copying them from someone.
I recently had someone on twitter ask if there were more Xsigo resources out there for research. He commented that it was really cool, but seemingly hard to find information. I tried to find good information that had some technical content (not just a press release). So I will post some links here and as I come across more I will update this post.
Special thanks to Kevin Miller (@kevin_miller), for making sure I didn’t burn up anything and running out to Fry’s to get a new CPU when the orginal we ordered turned out to be not compatible.
List of the material used in final Version:
Intel DH57JG – Motherboard
Intel i5-661 Core Duo – Processor (special note: DO NOT get the i5-655k unlocked CPU in the picture, it was not compatible with any intel Motherboard)
Lian Li MINI ITX Case (6x9x12 in dimensions) supports Full size PSU
Rosewill silent PSU
Intel dual port PCIe 16x Gbe NIC
Stock intel heatsink and fan (Nexus fan in the picture was very cool, just too big to fit anything into the PCIe port.
2x Intel 80GB SSD
2x4GB OCZ Memory Kit
The server built amazingly fast using PXE boot and installing an ESXi image. Only thing that didn’t work that I wish it did was the on board NIC, 2 GigE ports will be more than enough for our purpose. This is not a lab machine but will run all the components I need to deploy a solution in an automated fashion. I really like VMware Fusion but if I try to run Windows 7, a Linux Server and a Windows 2003 server at the same time my awesome Mac Book Pro becomes useless. This is a lightweight and easy way to bring all of these components together for relatively low cost and if it can save half a day on an install it will pay for itself pretty fast.
I am running:
Windows 2003 ( a vCenter Template)
UDA20 – Ultimate Deployment Appliance that I fought with for a while and finally have it running reliably.
vSphere Mangement Assistant
As of this post working on building:
Windows 7 VM (for Powershell and other tools)
Maybe a free NFS/CIFS server for some easy file shares.
Linux Server (just in case I need it)
Now for some pics:
Two 80 GB SSD’s are mounted in this space.
Everything going into the Case
Size relative to my hand
I do not have NBA player sized hands, hopefully this shows just how small the case is. This solution is a little more pricey for just a lab machine but if it travels I do not need a SATA disk failing because the server had a bumpy ride.
I usually don’t just make announcements on this site. There are plenty of good news sites that let you know what is new and whatnot. I don’t remember if I saw this but I am behind on my reader feeds so forgive me if everyone already checked this out. The View Open Client is an open client (hence the name) to connect to VMware View Managed Desktop deployments if your OS is Mac or Linux and this is very good news. The java plugin or whatever you call it from the View web manager is annoying to me mainly because the java security is pesky. I know you can just change the settings in Java but I have had in the past where an update from Apple kills my previous settings.
All this to say someone today had never heard of the client and I had show him what was up. He was very happy to be introduced to the View Open client. So I thought it would be cool to spread the word a little more.
Last Friday night I received an email from John Troyer at VMware inviting me to the vExpert 2010 program. It is an honor to be included with such a great list of people. I never know how to respond to be complimented. That is why I like high fives. It is like saying good job, but the only expected response is to high five back. No awkward thank you, or speeches needed. Just don’t leave me hangin’ and everything is understood.
I am extremely excited to get the VMware vExpert 2010, but since this is the internets, no one is here to high five.
Sometimes you may be required to run your vCenter server that has two network interfaces. One in the network it can be reached for remote desktop access and the other where it has access to the ESX servers in order to manage the VMware hosts. This is sort of a hybrid model of an isolated management network. Where only one host can reach the management ports. One thing to think about in this model is Update Manager by default will not like it. Everything may look ok, but trying to scan a host will fail. Luckily though it is an easy fix.
In the update manager configuration tab change the ip in the picture to the IP accessible by the ESX servers. Then remember to restart the Update Manager services. Now go back and run the ESX scan/stage/remediation.