I’ve joined @SolidFire

I am excited to share that I have joined the team at SolidFire as a Systems Engineer. For those unfamiliar, SolidFire is the market leader in all-flash primary storage systems built for next generation data centers and cloud service providers.


I look forward to working with an All-star team of colleagues, many of whom I’ve been fortunate enough to count among my friends and collaborators in various roles over the years.

In fact, knowing so many people who already work at SolidFire, I find it difficult to choose only a few to name to mention. So rather than attempting to do that, I’ll include a reference to @Mike_Colson, who announced last week that he too is joining the team. Mike followed up with a great post about Why SolidFire? on his blog. I share many of Mike’s views expressed in the post and rather than repeat them, I’ll let you go read them.

I will add that personally I believe what makes the solution exciting is that scalability is driven through the power of automation and open integration points for multiple platforms. Vendors’ ability to distinguish themselves today is by continued innovation and API exposure. In essence, revealing bits of their own secret sauce, such as the ability to provide hooks that can leverage underlying features where available and appropriate. Both HW and SW vendors began down this path with VAAI and VASA for Automated Storage Tiering, Storage DRS, I/O Control and additional capabilities are here now with VVOLs such as VM level of granularity and Quality of Service. Abstraction and granular control allow administrators to more easily manage environments with heterogeneous application demands without spreading their already divergent skill sets too thin. Additional abstraction of the storage layer also provides the options to assign and guarantee resources to meet specific needs without adding complexity or increasing storage management touch-points. </COMMERCIAL>

Looking ahead, this new role promises opportunity to continue to grow and learn.  I am especially eager to gain an even greater perspective on the demands of multi-tenant infrastructure technologies in use within many large Enterprise customers and dive deeper into integration points with VMware as well as OpenStack, and CloudStack.


When I left my previous position to join Dell I wrote about that here. In fact a good friend and now my colleague at SolidFire, Gabriel Chapman and I somewhat coordinated our individual career path announcements and you know that Gabe surely played a key role in bringing me over to the SolidFire family. Thanks man!

Here, I would be remiss if I did not also thank my colleagues at Dell and especially each of my direct teammates in the CCC and vWorkspace group for the experience working together. I’m certain we’ll continue to cross paths.

So, whether you’re one of my new or former colleagues or a member of this great Community, please reach out and say hello! I’m excited to begin this new chapter. I’ll be spending some time in Boulder, Colorado over the next couple weeks, so don’t be a stranger if you’re in the area.

Future posts are coming in which I’ll share a bit more about #vSensei but I want to mention here that I have been working with Cody over the past few months and am really happy about the results. More on that later. For now I’ll close with  Fake Grimlock: BE ON FIRE!



I’m changing jobs. Leaving @ProximalData after 2.5 years. More news to come

TL;DR I’m changing jobs. Leaving @ProximalData after 2.5 years. More news to come.

It seems not that long ago I left my previous position with a local university to join Proximal Data. Startup time is like dog years! 2 and 1/2  years, 37 generally available releases across 3 hypervisor platforms, early WebEx sessions, late WebEx sessions, pages and pages of tech docs and emails, along with many long hard hours and a whole bunch of learning later, I’m taking another leap. I’ll share where I’m heading in another post. It’s a role that I’ve been steering my career toward and I feel the time is right for this opportunity. In making my decision I consulted more than just my own heart, my head and my wife… though those are obviously high up in my decision tree. I also have to thank several members of this community for sharing their own experience and insight with me, whether directly via late night phone calls, dms, sms or indirectly via blog posts, podcasts, etc. These include my fellow vBrownbag crew, VMUG co-leaders and current or past employees of my future employer, as well as others who have ‘moved around‘ lately. For others considering making a move, I recommend in addition to feeling out your own network, check out  @JoshAtwell‘s blog posts on the subject at vTesseract.com and Gabriel Chapman @Bacon_Is_King ‘s blog posts, including #SNLDD #7: ‘When is it Time to Jump Ship?‘. I have to thank my team at Proximal Data for bringing me on for my first startup rodeo. I’d do it again in a heartbeat! It was everything and nothing like I’d imagined, all at the same time. Being lead by industry veterans who effectively married the best parts of being a startup with the lessons learned while at large corporations has shaped the lens I view future opportunities though. Working side by side with a senior team of incredibly capable engineers, not being a developer myself, was as challenging as it was inspiring. I am glad they believe in me as much as I have in them. I’ve strengthened my own capability to learn and grow and acquire a number of the skills that I will continue to build my career upon. This is a very amicable parting and I’ve discussed it at length with our CEO, our VP and my colleagues. I wish the company and my coworkers the very best!

#vBrownBag LATAM @VMworld 2014 sesiones recomendadas #VMUG y #vExpert, #VMunderground

The following content is in Spanish, the language in which the webinar is presented.
cross-post: blog: http://professionalvmware.com/?p=4659

El pasado 24 de julio, 2014 ProfessionalVMware.com  #vBrownBag LATAM presentó el tema @VMworld sesiones y recomendaciones por Larry Gonzalez, Kyle Murley y Randall Cruz.

(tip: se puede ampliar a pantalla completa y cambiar la calidad de reprodución a HD 720p).

vBrownBag en español es una expansión de la plataforma ProfessionalVMware.com para el crecimiento profesional y contribución a la comunidad VMware de habla hispana en América Latina, España y alrededor del mundo.

Desde que se anunció el lanzamiento de los vBrownBag en castellano como expansión de la plataforma ProfessionalVMware.com venimos grabando las presentaciones realizadas cada jueves a las 7:00 pm hora pacífico (PDT) (02:00 UTC).

Para facilitar el acceso al contenido hemos decidido hacerlo disponible por un canal de YouTube vBrownbagLATAM

Para no perder el webinar en vivo cada semana le invitamos a inscribirse como participante http://bit.ly/BrownbagLATAM

Seguimos reclutando presentadores

Los temas están por determinarse y serán representativos de la necesidad y capacidad de los participantes.

Se puede anotar como presentador en: http://bit.ly/BrownbagPresenter

¡Anímese a compartir y aprender juntos con los miembros de esta, nuestra comunidad vBrownbag en español!

esxtop This is why I love the #vExpert community! Thx @Mandivs @esxtopGuru @VMwareCares @VMwFlings

When I first began working with VMware virtualization tools it was not just the technology that got me excited.

What actually gave me the most incredible feeling was the community that surrounds this awesome tech. There are innumerable examples of how time and time again I found myself either wondering about something or actually at a roadblock and the community came through for me.

A few weeks ago I had yet another of these experiences, so I thought I should get it out there as a shining example of exactly what I’m talking about.

I was working on something for my day job that required me to use the tool ‘esxtop’ – an awesome and powerful commandline utility for performance monitoring and diagnostics.  (See DuncanYB‘s posts on esxtop for a good jumping off point )

What I encountered was difficulty using the tool in the way the documentation indicated it should work.

It seemed I either didn’t understand what I was supposed to do (totally possible), or esxtop didn’t work as it claimed to.

In esxtop when monitoring storage, you have the option to expand or roll up device(s) so as to get a more detailed view of information related to the specific device(s) you’re looking at.

Once you change to the esxtop ‘u’ view (storage devices), option ‘e’ prompts you to enter the device ID.

Screenshot expand naa.jpg

It seemed that for devices with an naa.  or mpx. ID it worked fine, but with the  t10.ATA IDs it seemed like either they were being truncated somewhere or possibly had characters that were not being escaped correctly.

Screenshot naa expanded.jpg

Feeling a little frustrated (or stupid) I posted this rather cryptic tweet w/the #vExpert hash tag:

Within hours just I received a response from @VMwareCares with a viable workaround.

Armed with this nugget of knowledge I went about what I needed to do, now able to expand the t10.ATA device(s) I needed to look at.

Screenshot 2013-08-07 at 11.25.38 PM

It didn’t end there though, the next morning  Krishna Raj Raja ‏@esxtopGuru elaborated further, stating:

Raj also indicated that connecting to resxtop via vMA would be another workaround.

The help kept on coming as Manish Patel @Mandivs indicated there was a VMware KB that covered this.

So, not only by sending out a quick tweet had I found a real solution to my problem, I also learned something very useful in other areas of esxtop.  All thanks to the power of the VMware community on Twitter and thanks to @VMwareCares, Raj, and Manish.

As if that hadn’t been enough, to “top it all off, that same afternoon a new Fling was announced:

This visual tool makes esxtop even more accessible and I’ve confirmed the expand/rollup issue is definitely not a problem here.

Have you had an exceptional experience with the virtualization community over Twitter? Drop a note in the comments or point us to your write up on it. I think it’s worth recognizing that none of us go at it alone, and we do depend on each other, so a thank you is definitely in order.

Til next time, see you on the Twitters — @kylemurley