I received my official letter today that I was welcomed into the 2015 vExpert Program. With this livevirtually blog I set out to post answers to questions people asked me that I thought would be useful to others in the community. To be recognized for this effort is rewarding and I am grateful for it. Thank you! Now I just need to keep doing it and I plan to. Click the badge below for the official announcement and full list of the many talented members of the 2015 vExpert community:
The big VMware vSphere 6 launch was yesterday and along with it comes Virtual SAN (VSAN) 6. Here are a couple of good summaries:
Rawlinson Rivera – VMware Virtual SAN 6.0
The big news is that a vSphere cluster will now scale to 64 hosts and thus VSAN will too. So what does that look like fully scaled up and out with the maximum hosts, maximum disk groups, and maximum disks per disk group? By the way, for details on how VSAN scales up and out check Is Virtual SAN (VSAN) Scale Up or Scale Out Storage…, Yes!.
Virtual SAN (VSAN) Enabled vSphere Cluster Scaled Up and Out to 64 hosts (nodes).
Oh yea, the overall VSAN performance is significantly improved. Plus with double the number of hosts that doubles the performance. In addition, VSAN now supports an All-Flash configuration that even further increases the performance.
I’ve been at VMware for 1.5 years and have had a blast talking to customers, partners, and VMware employees about all things software defined storage. This primarily involves Virtual SAN & EVO:RAIL which take advantage of VASA, Storage Policy Based Management, and VVOLS. Because we are talking about storage it also includes discussing the benefits of vSphere Replication, Site Recovery Manager, and vSphere Data Protection. Basically, anything to do with storing, protecting, and managing Virtual Machine data. Its exciting to be part of the whole software defined data center strategy.
We are growing our Software Defined Storage team and are looking for qualified rockstars. If you are one, and the topics above are familiar to you, and you are interested in joining the VMware Software Defined Storage Team, then check out the openings below. Feel free to apply directly or reach out to me with any questions at: pkeilty at vmware dot com
You can find the openings on the VMware Public Job Page: http://vmware.jobs/
Plug in the Requisition Number below to find more details on the openings and full job descriptions:
- Requisition Number 55635BR – Sr. Systems Engineer-Software Defined Storage-East in New York New York United States
We are also looking for SE’s in the Ohio Valley and South East USA. In addition, we are looking for a Technical Field SE in the East. These jobs Requisitions will be posted soon.
- Requisition Number 58265BR – Storage Account Executive in Austin Texas United States
- Requisition Number 58420BR – Storage Account Executive – Federal in Reston Virginia United States
- Requisition Number 58501BR – Sales Leader, Software Defined Storage – Palo Alto or Austin in Austin Texas United States
- Requisition 58504BR – Inside Sales Representative, Software Defined Storage in Austin Texas United States
Unfortunately I won’t be attending VMware PEX this year. Its a great event to meet up with our great VMware partners and learn the latest VMware tech. There will be tons of Software Defined goodness, specifically, here is a great link to all the storage stuff:
This may be stating the obvious but I think it’s worth repeating. Before building a Virtual SAN enabled cluster make sure:
- The server hardware is updated to the latest and greatest system ROM / BIOS / firmware
- The IO Controller is running the latest firmware
- The SSD are running the latest firmware
- The HDD are running the latest firmware
These firmware updates often resolve some important hardware issues.
Next, make sure you follow the Performance Best Practices for VMware vSphere® 5.5
- Specifically, make sure Power Management BIOS Settings are disabled in the server BIOS (see page 17)
Once ESXi is installed on the host
- Make sure the IO Controller is loading the correct version of the device driver. You can look this up on the Virtual SAN HCL
I work with a lot of customers who are evaluating or implementing Virtual SAN and following these simple, obvious, but important best practices have led to better performance and a better overall experience with Virtual SAN.
Recently, with the announcement of the availability of VVols in vSphere.NEXT I was asked to give a deep dive presentation to a customer with a focus on what VVols meant for protection VM’s. While at EMC as a vSpecialist I lead a group focused on protecting VM’s so this is something I’ve been interested in for awhile. I’m a big fan of RecoverPoint and am excited about virtual RecoverPoint’s ability to offer continuous data protection for VSAN as I indicated here. I’m also a huge fan of VPLEX and spent a lot of time during my days at EMC discussing what it could do. The more I dug into what VVols could do to help with various VM movement and data protection schemes the more I realized there was much to be excited about but also much need for clarification. So, after some research, phone calls, and email exchanges with people in the know I gathered the information and felt it would be good information to share.
What follows is kind of a “everything but the kitchen sink” post on various ways to move and protect VM’s. There were several pieces of the puzzle to put together so here are the past, present, and future options.
XvMotion (Enhanced vMotion) – vMotion without shared storage – Released in vSphere 5.1
In vSphere 5.1 VMware eliminated the shared storage requirement of vMotion.
- vMotion – vMotion can be used to non-disruptively move a VM from one host to another host provided both hosts have access to the same shared storage (i.e. A datastore backed by a LUN or volume on a storage array or shared storage device). Prior to vSphere 5.1 this was the only option to non-disruptively move a VM between hosts.
- Storage vMotion – this allows VM vmdk’s to be non-disruptively moved from one datastore to another datastore provided the host has access to both.
- XvMotion – As of vSphere 5.1. XvMotion allows a VM on one host, regardless of the storage it is using, to be non-disruptively moved to another host, regardless of the storage it is using. Shared storage is no longer a requirement. The data is moved through the vMotion network. This was a major step towards VM mobility freedom, especially when you think of moving workloads in and out of the cloud.
- For more information see: Requirements and Limitations for vMotion Without Shared Storage
Cross-vCenter vMotion – Announced at VMworld 2014, available in vSphere.NEXT (future release)
This new feature was announced during the VMworld 2014 US – General Session – Tuesday.
This is another fun short project I was fortunate enough to be involved in with a great VMware partner, PC Connection.
This is part of their “Virtualization and Cloud Are Here to Stay” podcast series. Thanks to PC Connection for letting me be a part of it.
One of the big topics at VMworld 2014 was VVols. VMware announced it will be part of the next release of vSphere and almost every storage vendor on the planet is excited about the benefits that VVols bring. I was working the VVol booth at VMworld and had the pleasure of being interviewed by VMworld TV to discuss the comparison between VSAN and VVols. This was fun but unscripted and off the cuff so here it is:
VMworld TV Interview: Peter Keilty of VMware Discussed Virtual Volumes
What I’m trying to say is:
- VSAN is the first supported storage solution takes advantage of VVols.
- VVols, in vSphere.NEXT, will work in conjunction with VASA to allow all block and file based storage arrays to fully realize the benefits of Storage Policy Based Management (SPBM).
- Each storage vendor can write a VASA/VVol provider that registers with vCenter to integrate with the vSphere API’s and promote their storage capabilities to vCenter. I expect just about every storage array vendor to do this. I have seen VVol demonstrations by EMC, NetApp, Dell, HP, and IBM.
- VVols eliminates the requirements of creating LUNs or Volumes on the arrays, instead, arrays present a pool or multiple pools of capacity in the form of storage containers that the hosts in the cluster see as datastores
- Through SPBM, administrators can create different service levels in the form of policy that can be satisfied by the underlying storage provider container.
- When VM’s get provisioned, they get assigned to a policy, and their objects (namespace, swap, vmdk’s, snap/clones) get placed as native objects into the container in the form of VVols.
- You can even assign objects from the same VM to different policy to give them different service levels, all potentially satisfied by the same storage provider or perhaps different provider containers. In other words, a vmdk for an OS image might want dedupe enabled but a vmdk for a database might not want dedupe but might want cache acceleration. Different policy can be set and each object can be assigned to the policy that will deliver the desired service level. The objects could be placed into the same storage array pool but taking advantage of different storage array features. And these can be changed on the fly as needed.
Like all the storage vendors out there, I’m very excited about the benefits of VVols. For a full description and deep dive check out this awesome VMworld session by Rawlinson Rivera (http://www.punchingclouds.com/) and Suzy Visvanathan:
Virtual Volumes Technical Deep Dive
I’m really looking forward to attending VMworld 2014 in a few weeks. Its a great time to catch up with friends and meet new ones. For me the week kicks off on Thursday at the VMware SE Tech Summit. Then vOdgeball on Sunday afternoon with a team of former EMC vSpecialists. This is a great event to help out a great cause, the Wounded Warrior Project. We’ll also be honoring our two vSpecialist friends, Jim Ruddy and Stephen Hunt, that were recently involved in a tragic accident. Then the main event starts Sunday night. It should be fun and exhausting.
Virtual SAN (VSAN) is sure to be one of the highlights of the show.
When starting a new VMware project or evaluating new features, it’s always good to start with the latest and greatest software versions. The following describes how to figure out what ESXi, vCenter, and Web Client you are currently running and if they are the latest build number. If not, you should consider upgrading.
Where can I find a list of VMware software versions and build numbers?
VMware vSphere and vCloud suite build numbers table:
How do I determine what ESXi build am I running?
Via the vSphere Web Client
- Log into the VMware vSphere Web Client
- Select a host
- Home à Hosts and Clusters à Datacenter à Cluster à Host
- Select Summary tab
- Find the Configuration box (likely somewhere at the bottom right of screen)
- “ESX/ESXi Version” will tell you the version and build number
Via command line
- Log into the ESXi Shell of a host either by enabling local access and use the local shell on the physical console or enable SSH access and connect via an SSH tool like PuTTY.
- Execute the following command
- vmware –vl
- Results will look something like this:
- VMware ESXi 5.5.0 build-???????
- VMware ESXi 5.5.0 Update 1
How do I determine what vCenter build am I running?
- Log into the VMware vSphere Web Client
- Locate the vCenter Server in the inventory tree
- Home à vCenter à Inventory Lists à vCenter Servers à vCenter Server
- Select the “Summary” tab
- The version is listed in the “Version Information” pane on the right (see screenshot)
How do I determine what vSphere Web Client build am I running
- On the vSphere Web Client
- Help —> About VMware vSphere
- The version is listed in the “Version Information” pane on the right (should look something like)
- vSphere Web Client: Version 5.5.0 Build ???????