If given a choice between these VMware-based specialities...

[itrsteve]

So I had a career development talk with my boss the other day and he wants me to choose a specialty as the vSphere/vCD-based engagements are obviously slowing down. I'm having a hard time deciding which route to take and really trying to be as diligent as I can about making the decision. I'm thrilled that he's giving me the option, but I'm trying to come to the decision rather quickly

The 3 options are
Automation & Orchestration (vCAC/vCO/PowerCLI)
End User Computing (The whole Horizon suite)
Network Virtualization (NSX/vCHS)

Here is my pro/con list

Automation & Orchestration
Pros:
- Highest in demand for PSO engagements currently
- vCAC is here to stay and will be an integral part of vSphere going forward
- A decent aptitude for automation tasks with other technologies, should be an easier learning curve/solid PowerCLI background

Cons:
- Highest in demand for PSO engagements currently (see travel, the random week at home every two months or so may not exist)
- Having to hear the word 'cloud' more than I could tolerate
- Having to hear people say vCAC instead of spelling it out

End User Computing
Pros:
- Solid background with View/decent with ThinApp
- Easier learning curve (outside of Mirage, I've had to work with everything)
- Mature technology, tons of training, support and reachback available
- Highly marketable skillset currently

Cons:
- Having to deal with End User crap (i.e. desktop applications, finnicky ThinApp deployments, printers, etc)
- Having to deal with PKI/smart cards and Policy/Compliance applications (i.e. HBSS)... two of my most hated things
- Engagements are convoluted/stalled by silo'd IT departments (systems, networking, storage, security, desktop, application teams). Having to dredge through org politics at customer sites to meet an objective in a timely manner... Not to say this isn't a valuable skill that I don't possess, just find it annoying at times.

Network Virtualization
Pros:
- Highly disruptive technology in the same manner that vSphere was. Makes it very exciting.
- A core infrastructure component like servers & storage, so designs will work with the architectural teams at each location
- Learning a new technology at the bleeding edge of VMware/industry offerings

Cons:
- Weaker networking background compared to other components of the stack. May make for tough discussions with networking teams to guide in willingly adopting disruptive technologies. Need to quickly gain a full grasp of all of the provisioning pitfalls that NSX will alleviate.
- Technologies are so new that internal support, training and enablement items are currently lacking behind the other 2 options.
- Potential to be so disruptive that it may not grab traction in the market to make a valuable skillset in the future... Not as convinced on this, but is still a concern.


At this point I'm leaning towards the NSX route for what it could do to the market, but I have yet to really see it in action. It's the offering I'm least comfortable with but most interested in if that makes sense.

Just curious what you guys would choose and why

 

[Thuleman]

Since you find End User Computing annoying it's really out, but that's what I'd focus on. I'd dump ThinApp and start deploying Unidesk to make your and your customer's lives easier by orders of magnitude.

 

[MysticRyuujin]

Decide on the one that you find more interesting...

I always tell people who want to make it in the IT field that it doesn't matter what position pays the most on average, what matters is how good you are at your profession and in order to do that you have to really like what you're doing...you have to WANT to learn, play, experiment.

 

[lopoetve]

So, your first and third are the same.

You cannot do vCAC/AppD work without a shitload of NSX/vCNS in there. Vice versa, no one does manual deployments of NSX - it's all automated. The two either co-exist or don't exist at all (and vCAC is pronounced v-cake).

Guess what - that's my world now, and it's a metric crap-ton to learn But it's a blast. Good luck! Got any specific questions you want to know?

 

[RESTfulADI]

Datacenter virtualization/administration/design track slowing down? I guess it depends on the location.

 

[Child of Wonder]

Datacenter virtualization/administration/design track slowing down? I guess it depends on the location.

Obviously there are very few "green fields" out there to set up virtualization for the first time with a client, but I'm still finding there are plenty of opportunities for data virtualization/administration/design with the clients I work with. Lots of people still aren't comfortable with upgrading vSphere, are running poorly designed environments, and have issues. Also, working with Cisco UCS I often get to design a new solution for someone as they change from rack mount or other blade vendors to UCS.

Given your three choices, I'd go the automation route though.

 

[RESTfulADI]

I'm booked a month out standing up, upgrading, expanding, and troubleshooting vCenter/vCops/UCS/n1000v/Storage.

 

[itrsteve]

Decide on the one that you find more interesting...

I always tell people who want to make it in the IT field that it doesn't matter what position pays the most on average, what matters is how good you are at your profession and in order to do that you have to really like what you're doing...you have to WANT to learn, play, experiment.

My position/pay isn't changing, just a specialty route that I have to focus on will. With that being said, I still want to make sure whatever product(s) that I have to get stovepiped into will have plenty of growth in the marketplace.

So, your first and third are the same.

You cannot do vCAC/AppD work without a shitload of NSX/vCNS in there. Vice versa, no one does manual deployments of NSX - it's all automated. The two either co-exist or don't exist at all (and vCAC is pronounced v-cake).

Guess what - that's my world now, and it's a metric crap-ton to learn But it's a blast. Good luck! Got any specific questions you want to know?

Yes and no. You're right that I'm not going to get out of going the NSX route without having to use vCAC; however, the engagements that I get will still be based around NSX/vCNS and not specifically vCAC/vCO

Since this is your world now, how are you liking it? You're on the GSS team right? Or was it CoE? I forget.

Datacenter virtualization/administration/design track slowing down? I guess it depends on the location.

It's not going anywhere, but being that I'm a PSO guy, the team has to have individuals that can collectively cover down on all of the product offerings. Can't be a jack of all trades now, there's just too much stuff. The easy days of only having to know vSphere, Converter and LabManager are long gone.

 

[lopoetve]

I'm CoE now - was GSS for a long time though. I'll get to your PM once I'm in Brazil (kicking back with house of cards before a 12 hour flight).

Love what I'm doing now

 

[defuseme2k]

I start with VMware PSO tomorrow.

I find some of this thread terrifying

 

[itrsteve]

I start with VMware PSO tomorrow.

I find some of this thread terrifying

You may not get the liberty of having such a choice.

Kidding, congrats! It's a fun ride, been doing it for 3 years with no intentions on stopping just yet.