Feb 19 2018

VMworld 2018 Call For Papers is open – here’s how to get people to vote for and attend your session

VMware just announced that the Call for Papers for VMworld 2018 is now open until March 13th. Just like last year, this year VMware has opened early compared to the usual March-April period of years past. Remember VMworld US is again back in Vegas this year at the Mandalay Bay from Aug. 26th-30th, VMworld Europe in Barcelona is much later this year, instead of being right after the US event like last year, this year it it pushed out to November (5th-8th). Here are the key dates for the CFP process this year:

  • June 12, 2018 – Speaker Resource Center Live (US and Europe)
  • June 19, 2018 – Content Catalog Live (US and Europe)
  • July 10, 2018 – Presentation First Drafts Due (US)
  • July 17, 2018 – Schedule Builder Live (US)
  • August 2, 2018 – Final Presentations Due (US)
  • August 26-30 – VMworld 2018 US takes place (Las Vegas)
  • September 25, 2018 – Schedule Builder Live (Europe)
  • September 25, 2018 – Presentation First Drafts Due (Europe)
  • November 5-8, 2018 – VMworld takes place (Barcelona)

Last year they ended up extended the deadline a few days, but one thing I can’t stress enough is don’t wait for until the last minute and rush through it, plan it out now and write your submissions up so they are well thought out. From previous experience I can tell you to have a catchy title as it’s your sessions curb appeal. Many people won’t make it past your title and you miss a chance to interest them with your abstract if you have a boring and un-interesting session title. As a former content committee judge I can also tell you to spend some time on your abstract and don’t rush to throw something together without thinking it through. I’ve seen lots of session proposals that lacked any real detail about what the session was about.

If you want to impress both the content committee and public voters who will determine if your session is approved I encourage you to follow the tips listed below for the best chance of getting your session approved. For sponsors in particular I highly encourage you to read this post I did last year entitled: Sponsor sessions at VMware events: If you build it right they will come. In that post I detailed what works and what doesn’t to make your session attractive to attendees, this is based on my personal experience at VMworld last year and how I was able to get almost 1,000 people to register for my session. To summarize the winning formula for a good session tends to be:

  • Knowledgeable, technical speaker + educational/technical content – sales/marketing pitch = great attendance

Here are some additional tips that VMware provides:

Tips for Creating Effective Titles for Submission

  • Do not use abbreviations or acronyms under any circumstances in the titles of your submissions.
  • Do not use competitor or other company names in your submission titles. If you are highlighting other companies within your session, you can adopt these names within the session description.
  • Start with the Benefit: Ex: Shorten Adoption Time by Using VMware’s XXX.
  • Use clear and concise language that attendees will immediately understand. The agenda will eventually host hundreds of sessions and attendees need to easily identify sessions of interest. Straight forward language like “Introduction to”, “Deep Dive” and “Case Study” are popular examples because they quickly tell the attendee important information about the session.

Typical Reasons for Abstract Rejection

  • The abstract is poorly written—ideas are not clear, goals are not established, there are grammatical errors, etc.
  • The content is not relevant to the indicated audience.
  • The session value is not clearly identified.
  • The session topic is not unique or overlaps with another more appropriate abstract.

Tips for Writing Winning Abstracts

  • Avoid beginning your session description with the phrase, “In this session we will…”, or “In this session you will learn…”. It does not add value and becomes tedious on an agenda of several hundred sessions. Instead try a rhetorical question, or an interesting industry data
    point to start your session abstract.
  • Ensure that what you submit will be what you present. Nothing will upset attendees more than signing up for a session that is not what it is advertised to be.
  • Your abstract should generate enthusiasm‐ make sure your content is relevant, but also generates excitement. What invaluable information will be shared during the session?
  • Thoughtfully leverage the tags in the system for topics, level, and roles. Who is the target audience? What products or topics does this session cover outside of the track name? What roles would specifically benefit from this session? Do not check every check box if your session is applicable to all.
  • Be Original – Attendees want to see new presentations that cover the latest innovations in technology. Take the time to create well‐written titles, abstracts, outlines, and the key takeaways for your submission. A thoughtful proposal will have a better chance of being
    selected and if accepted, will be seen by thousands of attendees once published in the course catalog.
  • Be Educational –VMware requires that sessions focus on the educational value of the presentation. Be sure that your proposal doesn’t sound like a sales pitch but rather an exciting opportunity for attendees to learn something new.
  • Be Timely – Make sure your topic is relevant to the audience you’re targeting. Review the content topics before submitting a session.

Read the full submission guidelines here and the FAQ here.

Share This:

Feb 13 2018

Automating Storage Provisioning using VMware vRealize Orchestrator

I finally got my company to get on board with an external webinar platform and I get to kick off the very first webinar on BrightTalk.The topic is on vRealize Orchestrator integration with the 3PAR platform as an example, I promise this will be a technical webinar and not a sales pitch so if you want to learn more about using vRealize Orchestrator & vRealize Automation with vSphere join us this Thursday 2/15 at 9:00am MST. You can sign up by clicking the below image, hope to see you there!

Automating Storage Provisioning using VMware vRealize Orchestrator

Virtualizing data center infrastructure has reduced server sprawl, and improved provisioning, scalability and TCO. However, it’s come with increased complexity in managing across the infrastructure stack. To address this, IT orgs are turning to automation. VMware vRealize Orchestrator and VMware vRealize Automation let you: easily provision virtual and physical servers, software, networking and storage; develop composite workflows to speed complex infrastructure provisioning; and create customized environments for dev/test. This webinar covers technical details of these products and includes a demonstration of how to start a VMware Private Cloud by automating Storage Provisioning tasks using the new vRealize Orchestrator plugin for HPE 3PAR Storeserv and vRealize Automation.
Share This:

Jan 25 2018

A new job for me and reflecting on 2017

2017 was a bit of a tough year for me mainly due to the major surgery that my daughter Sophia had and the subsequent very painful recovery from it. I’d have to say that was one of the most difficult and stressful things that I have been through in my life and I am very glad that it is behind me. I’ve very happy to say that Sophia is 100% recovered and is so much better off with her spine straightened, she was a trooper throughout it and was probably stronger than I was. I want to give a very big thanks to everyone that helped out with her trip to NASA that we took right before her surgery so she could have some fun before the surgery ruined most of her summer.

Once that was past it was great seeing old friends and making new ones at VMworld, as usual that was an enjoyable break from the normal work and home life experience. Shortly after VMworld I was approached by someone within HPE to fill in for someone who was leaving to go work for Zerto. She was the Product Manager for the HPE storage integration’s portfolio for VMware and with my background and experience that wanted me to fulfill that role on an interim basis why they searched for candidates to fill it permanently. This was all in addition to my existing job as Solutions Manager for VMware so essentially I was doing two jobs simultaneously.

I said I’d be happy to help out for a few months why they searched for candidates, I wasn’t really interested in taking the role permanently. It was definitely a change from my other job role in solutions were I was mostly a one man team, in the new role I managed the engineering teams that develop all of our VMware plug-ins which was a new and interesting job experience for me. As I waited for that position to be filled they came back to me a few weeks ago and expressed that they really wanted me to consider taking the job permanently. So after some consideration I decided to take it, they offered it in a way that I could keep some of my existing responsibilities around VMware solutions as well, so essentially I have dual job roles.

So effective Feb. 1 I’ll be the official WW Product Manager for our VMware storage plug-ins, which includes our plugins for vCenter (OneView), vRealize Ops Mgr, Log Insight & Orchestrator and SRM. I’ll also be continuing my existing role as WW Solutions Manager for VMware. So I’ll have plenty to keep me busy in 2018, if that wasn’t enough I’m also planning to move to the Houston area this summer. If you want to buy my house in Colorado, I’m sure Scott Lowe’s wife Crystal who is my realtor will love to sell it to you.

So that’s my update, I took most of December off and un-plugged from the virtual world for a while but I’m back and will be cranking out a bunch of posts here and also kicking off Top vBlog 2018 very soon.

Share This:

Jan 25 2018

2017 VVols year in review

I tend to write a lot about VMware VVols these days as I believe VMware’s new storage architecture has many benefits and VVols is the future of storage for vSphere. In this post I thought I would highlight and recap some of the posts that I did in 2017 related to VVols and you have many more VVols posts coming your way from me in 2018.

In January I gave an update on VVol adoption based on the data we collect from 3PAR arrays specific to VVols. I also showed how to find out which vendors support the new VVol replication feature introduced in vSphere 6.5.

In March I provided an overview of current storage vendor support for VVols which continues to grow.

In April I wrote about some of the new PowerCLI cmdlets that were released that support BC/DR operations related to replicating VVols.

In June I wrote about why their were almost no VVols session at VMworld 2017 as VMware felt they had done enough to promote VVols and it was now on the partners to do so.

In August I wrote about resources to learn more about VVols replication.

In September I wrote about a new report that IDC released that highlighted the benefits of VVols.  I also wrote on some of the enhancements that are in the upcoming vSphere release related to VVols. Finally I did a short post that highlighted an in-booth session that Pete Flecha from VMware did on VVols.

In October I wrote about how VVols inmpacts the protocol choices people make in vSphere.

In November I gave a fresh update on VVols adoption.

And in December I rested, more to come very soon!

Share This:

Nov 20 2017

A new update on VVols customer adoption

It’s been a while since I last reported on the customer telemetry data that we capture to track VVol adoption with 3PAR customers and wanted to provide an update. Before I share that I want to relay what I’ve seen and heard around VVols adoption in general.

VVols adoption is trending upward, our data confirms this and VMware confirms this as well. VMware can track some basic VVol stats via their vCenter analyst cloud functionality and the data I’ve seen that was shared to me by VMware definitely shows VVol adoption trending upwards. Adoption seems to trending up faster in the last year based on several factors:

  • More customers moving from vSphere 5.5 to vSphere 6.x were VVols is supported
  • The release of vSphere 6.5 which including the missing VVol replication functionality
  • Better partner support for VVols as partners build out their solutions and increase scalability
  • Better customer awareness of what VVol’s is and the benefits that VVols provides

Now before you get excited when I say trending upward there is still a very small percentage of the VMware install base currently using VVols, VMware estimates around 2%. However the usage trends have sharply up-ticked in the last year compared to the year and a half prior to that since the initial VVols release when adoption was almost non-existent. I fully expect that to continue to accelerate going forward as more customers start using it. So while adoption is on the rise which is a good sign I realistically don’t expect it to reach the tipping point of being the majority of what customers use (>50%) for several years.

As far as the development of VVols goes from a VMware perspective the VASA specification is basically feature complete. The roadmap for VVols is mostly minor enhancements and a lot of the under the covers optimization and support for things like in-band binding. Some of the other VMware product teams have some work to do to improve VVols support (-cough- SRM -cough-) but for the most part VVols is done. Partners have everything they need to build out their VVols solutions however they see fit based on the VASA framework and that really is the main inhibitor to VVols adoption, partner readiness with their VVols support.

So now on to the tracking data on 3PAR, this is an update since my last post on VVols adoption in January 2017 and a comparison from January 2016 to September 2017.

Jan 2016Jan 2017Sept 2017
Systems running VVols46258361
Systems with < 10 VVols36111165
Systems with 11-50 VVols55171
Systems with 51-100 VVols31135
Systems with 100+ VVols24390
1st largest customer (by # of VMs)N/A1,457 VVols/576 VMs2,656 VVols/727 VMs
10th largest customer (by # of VMs)N/A477 VVols/169 VMs944 VVols/216 VMs

As you can see from Jan. 2017 to Sept. 2017 VVols adoption has picked up and their are a good number of customers running it full scale (100+ VVols) in their environments. There also are some pretty significant size VVol deployments which is encouraging to see as the benefits that VVols provides are amplified the larger your vSphere environment is. I’ll be anxious to see what the data looks like 6 months from now as VVol adoption is only going to drive upward, however at what pace is yet to be seen. As partners continue to improve their VVol feature support and increase scalability it will help accelerate adoption going forward. The future for VVols looks bright and I look forward to the day when VMware finally retires VMFS and storage management is all policy based.

To learn more about VVols here our a few recent posts I did on various VVols topics:

Share This:

Nov 14 2017

How Pat Gelsinger saved VMware

I ran across this recent article in the SF Business Times and thought I would share it along with my thoughts. The article highlights VMware’s CEO Pat Gelsinger as one of the most admired CEO’s and how he helped right the VMware ship adrift in stormy seas during his tenure. You can read the article yourself but I thought I would share a few highlights from the article and a bit of Pat’s background I found out through my own research:

  • He grew up in rural Pennsylvania and worked on the family farm raising dairy cows, pigs, soybeans and sorghum. He expected that he would follow in his father’s footsteps as a farmer. An early interest in technology changed his career forever.
  • By age 18 he had an associate degree from Lincoln Tech and then headed out to Silicon Valley to work for Intel as a quality control technician. He soon discovered he wanted to be on the other side as an engineer and earned his electrical engineering degrees at Santa Clara University while working at Intel.
  • He worked at Intel for 30 years (1979-2009) initially as a technician and chip architect, he worked on the 386 processor (and wrote a book on it) and rose up to be the chief architect for the 486 processor. He then worked his way up the ladder to become Intel’s 1st CTO (2005-2009), he was also Sr. VP & GM for Intel’s Digital Enterprise Group.
  • He worked as President and COO at EMC until August 2012 when he was introduced as VMware’s new CEO at VMworld and took over the role from Paul Maritz. At the time VMware was struggling and threatened by cloud storage and needed to find the right path to better compete.
  • He helped create a winning strategy by shifting VMware’s focus to the cloud and forming key partnerships with major cloud players. He also helped navigate the Dell deal and ensure VMware’s independence all while going through a tough period in his personal life while his son battled cancer (he beat it!).
  • He’s a very spiritual person with a strong Christian faith who preaches and does a lot of charitable work. He has also written a few books which includes The Juggling Act: Bringing Balance to Your Faith, Family, and Work (2008). His favorite bible verse and life motto is Colossians 3:23: “Whatever you do, work at it with all your heart, as working for the Lord, not for human masters.”
  • He is a very charitable person and gives away almost 50% of his gross income to charity a big part of which goes to helping children in impoverished nations go to school, he also splurges a little on himself and owns a BMW i8 which is one sweet ride.

From my viewpoint I can’t think of a better person to lead VMware into the future, VMware has adapted to the ever changing IT landscape pretty well and it’s a testament to their leadership that they have made the changes necessary to stay relevant. It’s fairly unusual to have a CEO of a big company that has a deep technical background, many CEO’s are more your stereotypical executive business types. I think Pat’s management style of being a blue collar CEO who is very hands-on and deeply entrenched in the software that VMware develops is part of the reason they continue to be successful at what they do.

It’s readily apparent that he is very passionate and intense about what he does and his success over the years rising all the way to the top position at VMware is a testament to all his hard work and strong faith that made it possible. One of my favorite stories of his and how he was first introduced to VMware, he and Mendel Rosenblum (VMware co-founder) were back stage at a Intel developer conference the day after the very first vMotion and how Mendel was so excited and they sat there brainstorming use cases for it.

On a personal note I’ve met Pat several times at VMworld, mainly at vExpert events were he has appeared at. He is easily approachable, willing to talk to anyone, very laid-back and obviously a geek at heart like myself. I really like his casual, easy-going approach to things even in keynotes which is in sharp contrast to Paul Maritz who seemed very stiff and formal. His humanitarian work is truly inspiring as it shows he truly cares about those that are less fortunate. In one week he went from the main stage at VMworld 2017 speaking to thousands about technology to Kenya to help children and families in need.

I’ve always admired Pat Gelsinger, he’s a brilliant technologist, a wonderful leader, and an incredible person and VMware is very lucky to have him at the helm. Thanks Pat for all you do for the virtualization community and for the entire world, you are an inspiration to us all.

Share This:

Oct 31 2017

30 Must-Read Small Business IT Blogs 2017

I was recently honored to be included in a list of 30 must read SMB IT blogs and wanted to say thank you to BizTech for including me in that list. I looked through the blogs in that list and there is a lot of diversity in it with everything from credit card blogs to business blogs to general IT blogs and more. The only other blog on that list beside mine that I recognized was Tom Hollingsworth, the Networking Nerd blog. So thank you again, it’s always nice to be recognized and I will do my best to keep this blog interesting and informative.

Share This:

Oct 30 2017

How VVols impacts storage protocol choices with vSphere

File vs. Block, why choose one over the other with vSphere. They both have their pros and cons which has influenced decision making when it comes to picking your storage with vSphere but VVols has changed the game of how storage protocols interact with vSphere which may also impact your decision making.

Let’s first look at File (NFS), here’s some of the characteristics and pro’s/con’s:

  • File system is managed by the NAS array not vSphere
  • Uses an NFS Client build into ESXi to connect to NAS array via standard networking
  • Simplicity, no LUNs to deal with, easier to re-size volumes and easier overall management
  • VM’s are stored as files on a NAS array so the array can see and interact directly with individual VMs
  • Historically VMware feature development has lagged behind block

Now let’s first look at Block (iSCSI/FC), here’s some of the characteristics and pro’s/con’s:

  • File system managed by vSphere and not the array (VMFS)
  • Uses an iSCSI software initiator built into vSphere or physical HBA to connect to an array via either standard networking (iSCSI) or a FC fabric.
  • More complex, lots of LUNs to create, manage and re-size
  • VMs are stored as files on VMFS file system, the array has no visibility inside the LUN to see and interact directly with VMs
  • Historically VMware development more focused on block for new storage features

From this you could deduce that File is simpler and easier to manage and has VM-level visibility where Block has more management overhead and no VM-level visibility. Why is VM-level visibility a big deal? Because if a storage array can see individual VM’s then storage array features and capabilities can be applied at much more granular level rather than doing it at the LUN (VMFS datastore) level. The advantages of VM-level visibility include:

  • Ability to instantly reclaim disk space without UNMAP as the array knows when a VM is deleted or moved
  • Being able to snapshot or replicate individual virtual machines
  • Leveraging array based monitoring tools at the VM-level to see performance and capacity statistics
  • Easier troubleshooting at the array level to correlate VM to storage bottlenecks and hotspots
  • Using array based QoS tools to more granularly apply resource controls on VMs
  • Ability to place VMs directly on specific disk tiers to meet performance and resiliency SLAs
  • Being able to apply other array features such as de-dupe, compression, thin provisioning, etc at the VM-level

So VVols levels the playing field between file and block and puts them on equal footing with vSphere as VVols (VASA) essentially dictates a common framework and set of rules that all protocols must use for writing data to a storage array. The result of this is Block storage gains a huge advantage and puts it right on par with some of the advantages that File has always had with vSphere with simplified management and VM-level visibility. The below tables summarize the impact that VVols has on file and block storage arrays with VVols and how the storage protocol used becomes mostly irrelevant with VVols.

Table 1 – Comparison of File and Block protocols without VVols

Host AdapterI/O TransportHost PresentFile SystemVM StorageStorage Visibility
FileNFS ClientNetworkMount PointArray managed - NFSVMDK filesVM level
BlockiSCSI initiator (sw/hw) or HBANetwork or fabricLUNsvSphere managed - VMFSVMDK filesDatastore level

Table 2 – Comparison of File and Block protocols with VVols

Host AdapterI/O TransportHost PresentFile SystemVM StorageStorage Visibility
FileNFS ClientNetworkStorage ContainervSphere nativeVVolsVM level
BlockiSCSI initiator (sw/hw) or HBANetwork or fabricStorage ContainervSphere nativeVVolsVM level

As you can see VVols is a big deal for block storage arrays and essentially the storage protocol with VVols is now more about the method of how data is communicated to the storage array. The other things like how the file system is managed and VM-level visibility are not different anymore between protocols as vSphere natively writes VVols to an array without a file system and both file and block have the same VM-level visibility.

So now when it comes to choosing a storage protocol with vSphere it becomes more about the physical and networking layers between the host and the storage array. Things like bandwidth and network infrastructure will mostly drive the decision, fiber channel has obvious advantages but can be more costly and complex to implement but iSCSI and NFS are essentially almost the same now as they both use software clients built into vSphere and the exact same networking infrastructure.

With no more LUNs to deal with when using iSCSI for VVols it becomes a more attractive choice to use with vSphere bringing some of the same benefits as NFS around simplified management and VM-level visibility all delivered within VMware’s standardized vendor neutral Storage Policy Based Management (SPBM) framework. So what storage protocol will you use? Whatever you choose VVols has made the decision making a lot easier.

Share This:

Older posts «

» Newer posts