vmware | CrashLoopBackoff

Book Review: Automating vSphere with VMware vCenter Orchestrator

So to be 100% honest I have had this book on my desk for several months. Just staring at me. Calling my name. VMware press provided this copy to me along with Mike Laverick’s SRM book and so I am finally going to review the first one.

Cody Bunch does an amazing job of breaking down one of the most mystifying yet powerful products hidden in the VMware portfolio. VMware vCenter Orchestrator is almost mythical in the promises of automation of typical tasks of a vSphere administrator. While you can bang your head against the wall for weeks trying to figure out how to properly setup the vOrchestrator server and client I was able to use Cody’s guidance to have to operational and running test workflows in just a few hours (I am a slow reader).

I can’t stress enough the need for automation and orchestration in today’s virtual machine environment. The business is demanding more and more from the Virtualization team and in order to deliver vCenter Orchestrator is a good start since you probably already OWN it.

Hopefully soon there will be an update with information on the vApp version of Orchestrator. Check it out here on Amazon or your favorite book reseller.

Thanks again

The VMWorld 2012 Voting Post

I decided to wait a couple of days after the posturing/begging/campaigning died down. So that I could start it up again!

Shameless plugs are not usually my thing. I have been learning from @vTexan so here goes.

Make sure you sign in here to vote http://www.vmworld.com/www.vmworld.com/cfp.jspa

There are literally 9 Billion entries this year. So here are a few I like:

By the way I am stoked for a joint EMC / NetApp Session that doesn’t have Chad and Vaughn (no offense guys).

Finally, my title didn’t make the cut (View 5.1 and Storage so Awesome you’ll slap yo Mama OR Things only Ninjas know, behind the scenes with View 5.1 Storage Architectures) but here is my session on View 5.1 and Storage Deep Dive with EUC Ninja Mark Ewert.

Title:		View 5.1 Storage Features Deep Dive

Subtracks:		Desktop Virtualization
Tracks		End-User Computing
Technical Level		Advanced Technical
Area of Interest
Abstract:		Presented by VMware and EMC, this session will provide an in depth exploration of the new View 5.1 features related to storage optimization including the View Storage Accelerator (CBRC) and View Composer Array Integration (VCAI). The discussion will also provide detailed results of a joint VMware / EMC study quantifying the benefit of these new storage features and their resulting impact on virtual desktop density and the EMC VNX Storage Area Network used in the testing. To enable attendees to perform their own analysis, an overview of the LoginVSI virtual desktop benchmark system and test methodology used to obtain the results will also be provided.

So remember to Vote. Do it for the Children!

View Client on iPad with Bluetooth Keyboard

I was very excited to try out my View desktop using my new ZaggFolio Keyboard case. I did not have a chance to try out the View Client with the keyboard until today. I was sad to find out the keyboard does not work very smoothly. So I would like to point this out:

First you have to tap the keyboard icon in the top menu. Not sure why this exists, but it would be great if the keyboard fully worked. The keyboard fully working would be great because using the on screen keyboard it uses the half of the screen.

Anyone else think this is kind of weird?

Some Reality for us Infrastructure Peeps or Apps are cool too

Don’t’ you just love double titles?

For many years I have been an infrastructure guy. I really liked how the cables, and processors and Memory and blinking lights worked. Applications were often the necessary evil tolerated so that I can play with cool technology. During my own journey toward learning about the cloud it becomes increasingly important to consider the function of the application. Six years ago me would totally punch me in the face right now. Traitor. J

1 – Don’t get your App messed up in my resource buckets of awesomeness

So the reality check to the Infrastructure geek in me is this: The application teams really think of what you do as the network. That is why when anything is ever wrong it is always “the network’s” fault. What we love to do is getting abstracted more and more. I will still contend that is very important and very hard to do. Whether you are building reference architectures or deploying a converged infrastructure appliance almost no one but us cares. They just want the data to do their jobs. So while we have really great discussions about speeds and feeds, the guy in the picture below just wants the app. From the hypervisor down we need to design with the application in mind or we will risk becoming like that goth dude locked in the server room on IT Crowd.

2 Honey badger don’t care about FCoE

My next post will get into what I have been researching regarding what is out there and hopefully help us (infra. peeps) understand our App/Dev brothers better.

You are probably an Infrastructure person if:

You read this blog.
You work mainly with Virtualization
Storage Admin
Network Admin
You like to make fun of DBA’s

Extents vs Storage DRS

I was meeting with a customer today and had to stop for a second when they said they were using 10 TB datastores in vSphere 4.1.

At first I was going through my head of maybe NFS? No they are an all block shop. Oh wait yeah, extents. They were using 2 TB -512 byte luns to create a giant Datastore. I asked, why? The answer was simple, “so we only manage one datastore.”

I responded with well check out Storage DRS in vSphere 5! It gives you that one point to manage and automatic placement across multiple datastores. Additionally you actually can find which VM lives where, and use Storage Maintenance mode to do storage related maintenance. Right now they are locked into using extents. If they change their datastores into a Cluster the gain flexibility while not losing the ease of management.

I wanted to use the opportunity to list some information I think about Extents with VMware.

Extents do not equal bad. Just have the right reason to use them, and running out of space is not one.
If you lose one extent you don’t lose everything, unless that one is the first extent.
VMware places blocks on extents in some sort of even fashion. It is not spill and fill. While not really load balancing you don’t kill just one lun at a time.

An extent with a datastore is like a stack of luns. Don’t knock out the bottom block!

Some points about Storage DRS.

Storage DRS places VMDK’s based on IO and Space metrics.
Storage DRS and SRM 5 don’t play nice, last time I checked (2/13/12).
Combine Storage DRS with Storage Policy and you have a really easy way to place and manage VM’s on the storage. Just set the policy and check if it is compliant.

A Storage DRS cluster is multiple datastores appearing as one.

Some links on the topics:

Some more information from VMware on Extents
More on Storage DRS (SDRS)

In conclusion, SDRS may be removing some of the last reasons to use an extent (getting multiple lun performance with single point of management). Add that to being able to have up to 64 TB Datastores with VMFS and using extents will become even rarer than before. Unless you have another reason? Post it in the comments!

VMworld 2010 – In-N-Out Burger Meetup

Last year we had a great time going to In-n-out. For someone like me that was born and raised in Southern California, In-n-out is one of those things I must have when coming back to California. Luckily there is a location within a short trolley ride of the Moscone Center / VMworld 2010. If there is a lesson from last year if you are not used to public transportation you may need some practice. 🙂

Leave a comment or hit me up on twitter @2vcps if you are think you will make it.

Meetup
Where: at the In-n-out in San Francsico
When: Tuesday 8/31 at 5:30 pm – Gives you enough to go eat and come back before any Vendor sponsored party/events. I won’t interfere with free food and beer. 🙂
What: Eat Double Double, Fries

UPDATE

@trey_anderson was cool enough to make this map with directions from Moscone to In-N-Out

All out of HA Slots

A few weeks a go I was moving a customer from an old set of ESX servers (not HA clustered) to a new infrastructure of Clustered ESX hosts. After building, testing and verifying the hosts we started moving the VM’s. It became apparent after a little while there were some resource issues. After just a few VM’s were moved an alert appeared that we could not start any new machines. I start looking at the cluster and there is plenty of extra Memory and CPU. Still nothing will start.
I say to myself, “Self, we have read about this before.” I thought back to this HA Deep Dive article by Duncan Epping.
Lets check the HA slots! (on a side note, if you use HA and have never read the Deep Dive, go do it now!)

As you can see here the slot size is rather giant. We have the largest CPU and Memory reservation plus some overhead (for simplicity) and that blows the size of the slot way up. I didn’t set the reservation, but surely they were there. 8GB of reserved memory. 4000MHz of CPU. Ouch. Where did that come from? It followed the VM from the old host to the new one. One of the reasons I was there was to setup a new cluster since the older ones were performing so slow on the local storage. It seems like someone tried to help some critical VM’s along the way by adding the reservations. I removed the reservations and had plenty of slots as you see below.

Yeah! I was able to power on another VM!

The new cluster blew away the old one. Went from older Xeon’s to 6 core Nehalem’s, from local disks to 48 disks of Equallogic Storage. The reservation was no longer needed.

Lessons:
1. Be careful with reservations, it can impact your failover capacity.
2. Reservations set on the machine will follow it to a new host.

The Mini ESXi 4 Portable Server

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:

Before:

SSDs Mounted

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.

Update Manager and Isolated ESX Service Console Networks

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.