3V0-622 VCAP6-DCV Design Objective 3.1

 

I love participating in the vBrownbag, because it helps me refresh my both my technical knowledge and public speaking skills. Seems I always try to reduce the ums and ahs, but it still requires practice. Here’s the video and the slides. Enjoy!

EMEA – VCAP6-DVC Design Objective 3.1 with Joe Clarke

Youtube

Slides

 

Posted in Uncategorized

The Convergence of the Sysadmin Roles

With the convergence of networking and shared storage into compute, we’re seeing a pretty unique transition from a professional skills standpoint, that has been a fairly slow adoption curve. My take on the matter in regards to why HCI and SDN has been slow to adopt is predominantly because it involves people and updating of skill sets. Let’s take a look at a comparative example. To illustrate this point, lets look at a non-technical example. If you’re building a house, you definitely need these three roles:

  1. Carpenter
  2. Plumber
  3. Electrician

carpenter plumber electrician

Each of these roles:

  • Has a skill that has been learned over time, usually more than 3 years.
  • Is typically well defined in scope.
  • Is related to, but not solely dependent upon knowledge of one another.
  • Has knowledge of what’s basically going on with the others, but not in-depth knowledge.

So imagine what would happen if I walked up to a team of the above subcontractors that were going to work together on a construction project, and told them:

OK, you guys I need to install a new kind of walls that are prebuilt frames, with pipes and electric cable already run inside.

Well, that’s probably going to cause a lot of grief initially. Why? Because the plumber may have issues with how he’s going to hook up to pre-run pipes, because the electrician is going to have to splice a wire run in rather than a home-run to the panel, and the carpenter has nothing to do but bolt it to the ground. Any way you slice it, it might seem that it is removing a big part of their value.

If you haven’t figured it out already, the analogy I’m drawing here is to the:

  1. Carpenter – Compute/Server Sysadmin
  2. Plumber – Network Administrator
  3. Electrician – Storage Administrator

Also, the new building blocks are representative of HCI with SDN.

A big point that is missed here is that the value of these new building blocks is NOT, to the construction crew. The value of these new building blocks is to the customer, who can get much better time to value and reduce complexity by converging the architecture. Now, the illustration doesn’t completely work, because pre-built walls, come on, that really wouldn’t work. But it does apply to technology stacks.

So what’s the real barrier to success?

What if you told an electrician he would suddenly have to learn carpentry and plumbing? There’s definitely going to be some pushback. Same has been true with HCI in IT shops, those who are protective of their role and skill are typically barriers to change of any kind, but especially one which has potential to reduce their relevance if they do not retool their own personal skillsets. Like it or not, this is the cloud engineer of the future. The roles are converging simply to follow the trends which are providing a return the ultimate customer, the business. If the business sees that they get a faster return with consolidated technology, the technologists must follow this trend and start to branch into the other areas of expertise.

handyman

So what’s the point of this post?

As a consultant of 5 years who was a sysadmin for 7 years, my advice to Sysadmins is to stay relevant or prepare to die on the vine of your beholden technology alignment. Unlike the carpentry, plumbing and electrician industries, the technology industry seems to turn itself on its head every 5 years.

 

 

Posted in Uncategorized

Nobody cares what kind of undershirt you’re wearing. (Or what your hypervisor is)

mrdavis underftt nanodry champion hanesfruit

When was the last time you judged somebody because of the brand and type of undershirt they were wearing? Likely never. You may have judged someone for NOT wearing an undershirt (ugh), but that’s a different story. Nobody cares what kind or brand of undershirt you’re wearing. Except for one person. You. Why is that? What do you consider when you’re at the store and need fresh undershirts?

You probably care about several things:

  • YOU want to be comfortable. This is the primary reason you stick with an undershirt brand or type, typically regardless of cost.
  • YOU want to look professional. Wear an undershirt. My fellow dudes, wear one.
  • YOU have to pay money for these shirts, so they can’t be ridiculously over priced compared to alternatives.
  • YOU do not want OTHERS to perceive you as bad-smelling.

One of these bullet points has something to do with others. And it’s the last one. Arguably, it’s the single most important reason to wear an undershirt.

When it comes to your choice of hypervisor:

  • YOU want to be comfortable with the technology choice
  • YOU have to pay for your platform (sometimes the software, at the very least the hardware and support)
  • YOU do not want OTHERS to perceive you as providing a bad smelling platform and application experience

The point I’m trying to make here is, your personal preferences for Xen, KVM, vSphere, OpenStack, Hyper-V are just that. Your preferences, battle scars and stories are all about you and your perspective. You also care about others understanding the success you’ve had and enjoyed with solutions in the past.

If you’re a Linux guy with a beard to your belt, you might be more apt to support a KVM environment simply because you can make it do what the others can for less capital software investment, and because you can operate it immediately with less training. Alternatively, if you’ve traditionally been a Windows administrator, perhaps you’re more apt to pay for vSphere, because of familiarity and the ease of implementation and integration. You might be all in on the Microsoft stack and Hyper-V it makes sense given severe cost restrictions and lack of Linux administration experience.

What you prefer, may simply not be the best fit for what you are trying to accomplish, but not for the reason you might think.  When looking at TCO, you have to look at everything involved in a solution, including the salaries for human resources that can run it, cost of hardware, training, support and software.

All the personal preferences, feature capabilities, doesn’t mean anything if you as an IT professional at the end of the day you can’t provide:

  • Availability – High uptimes for your platform and application
  • Manageability – Your people can own the solution stack. Also, you can easily provide access to consumers.
  • Performance – You can size your platform to fit your workload with excellence
  • Recoverability – You can recover your solution after accidental deletion or destruction
  • Security – Your solution has an update lifecycle and can meet the business security requirements.
  • Cost – The solution must operate within the financial constraints.

You can build an on premises cloud today with a standardized HP cloud type server with a standard Ubuntu build and Docker. You can build it with Nutanix and KVM or vSphere. You can build it with vSphere and VxRAIL or VxRACK. Why do you ultimately pick up one over the other? Mostly the same reason you pick an undershirt from the aisle.

If it meets the requirements, you won’t smell bad, and it doesn’t break the bank, it sounds like you’ve got a winner. But just like I don’t care what kind of undershirt you’re wearing, I guarantee you that your end users don’t care what kind of OS on a hypervisor you’re running. They care how well you run their applications. So if your platform choice is ultimately impacting the business or causing them to perceive you in a negative light to due lack of availability, high time to value with capital expenses, or the inability to recover lost information, you might be looking at an indicator that you need to check the market. If not, keep your eye on the cost meter and keep on truckin’.

**Disclaimer: While the illustration used in this post does cater more specifically to men, it is not meant to be gender inclusive. There are tons of excellent IT professionals who are women, to whom this article applies to equally.

Posted in Uncategorized

PIVOT!

pivot

I ask people these three questions when they are considering new opportunities for their career:

  1. Is it doing what you love?
  2. More time at your home?
  3. Is it better for you financially?

The past few weeks have been pretty tumultuous at the elgwhoppo house. When your current employer wants to keep you, it’s a usually good thing, because typically you’ve shown value and are a hard worker. When they “go to the mattresses” to keep you, it’s usually an excellent thing, because they see you as a critical piece of the organization’s culture and success. As a result, I’ve been wrestling with those aforementioned three questions over the past few weeks.

The comments about innovation I made in a prior (since removed) blog post remain true; channel partner organizations must innovate and show value on the front end of business by identifying disruptive and profitable technologies and aligning resources and strategy in order to be successful. As I’ve moved through the conversations these past few weeks, it was apparent that I had a massive choice to make. Either I could up and walk from the challenges of front end innovation in the channel and keep myself headlong on the technical boots on the ground path and eventually pivot into management, or I could stay and pivot now to be a part of the team that’s on the bridge of the ship, helping provide direction for the ship course. My decision speaks for itself, as I am now a Principal Architect at Rolta AdvizeX.

In my new role, I will be architecting solutions beyond the marketing to help customers work through the real challenges that come with Hybrid Cloud and Digital Workspace solutions. I am excited to drive new innovation and continue to provide significant value at AdvizeX. From here on out, I start to lean more into people and process to accomplish objectives, rather than mostly technology. It’s a bit of a scary change, but hey, if you never move away from the things you’re comfortable with, you will never grow. Here’s to never stopping the growing and learning.

 

 

 

 

Posted in Uncategorized

Sharks and Security Tech

So I saw this news story over the weekend and honestly after watching the video, the first thing I thought of was firewalls. Kind of sad that this is the first analogy I drew from this, but that’s OK. It goes with the turf.

shark.png

So often in IT we bet on a technology to keep us secure, whether that be next generation firewalls, process whitelisting, anti-malware, network segmentation, and all of these are good things, no security consultant should ever argue against the concept of defense in depth. The problem is that we can end up shifting our thinking once we have these technologies in place that we are “good”, or that we’re “safe”.

Here are some examples of those thoughts:

  • “We have new next generation firewalls, nothing can get us now”
  • “We segmented off all our DB servers, we should be good now”
  • “We have no admin on any user boxes and antimalware everywhere”

I’m wondering how many cages that diver is going to trust after this terrifying diving experience. I bet netsec employees that have suffered a serious breach probably feel the same way about some of these technologies.

The point I’m trying to make with this post is that I never would have thought something like this could happen; those cages were ENGINEERED to withstand any kind of shark coming at it.

Understanding how you perceive technologies that you are a fan of is extremely important. Always understand your personal status quo and your thoughts and feelings around how you’ve been successful with a particular product. Don’t let success modify your thinking that a particular solution is impossible to break or breach, because that trust can very easily turn to complacency. Just because it works and reduces threats doesn’t make you bullet proof.

On an updated note, I’m updating my bucket list and removing an item.

 

 

Posted in Uncategorized

The Digital Workspace – I Fight For the Users

The Digital Frontier Workspace
tron_1982_movie_poster_01

In the 1981 version of the movie TRON, there is a phrase that TRON says and sort of defines his purpose. The phrase he uses is “I Fight for the Users”.

Having become a VDI/Presentation specialist over the past several years, I’m pretty sure I’ve felt this way several times. At the end of the day, our job as IT employees is to provide value to the business. Below is a quick list of things I’ve done in the past that felt like I had to “Fight for the users”

  • Proved the need for more compute resource for overly dense environments
  • Rationalize the upgrade of underperforming storage
  • Justified the value of graphics capabilities inside a remote session
  • Worked with IT departments to enable faster and less disruptive delivery of updates and net new applications
  • Troubleshot performance, network and software issues that were impeding progress of application delivery

The transformation of “remote access” to “Digital Workspace” has been a very long time coming, and for the most part the concept isn’t new. The new catch is that with the prevalence of SaaS becoming a normal delivery method of applications, this can add a great deal of complexity when attempting to deliver all the applications someone might need in a “one shop stop”. This was the message from the stage at VMworld this year. “Consumer Simple, Enterprise Secure” was the verbiage Sanjay Poonen used. He also used the term “Sesame Street Simple”, to describe the end user experience for signing on and accessing applications safely and securely, with a fast and simple BYOD enrollment process.

Here is where it gets fuzzy, the “Sesame Street Simple” concept in my opinion does not necessarily apply to the engineers and architects behind the solution. It’s the same when developing software, in order to make it simple for the end user it requires a very high amount of complexity on the backend to make it work with as simple of a workflow as possible. We can simplify on portions of the tasks such as the storage and compute expansion with the prevalence of HCI, but overall, providing a one shop stop to on-prem and SaaS based apps with one sign-on action is a daunting task. It’s for this reason that I bring up the concept of fighting for the user, this is not an easy task. It’s a fight that we must constantly keep in mind, that we are in the business of enabling the business, and therefore the users, regardless of where the applications reside. I fight for the users, and sometimes that means against IT departments who are reducing their value proposition in a fast shifting SaaS landscape. If you cannot service the business with an acceptable SLAs or timely responses, shadow IT will creep in, and/or it will cause damage to the organization.

Myself, I will continue to propose solutions that ATTEMPT to make lives easier for both end users and the engineers, but the very nature of making it simple on one side of the equation will almost always make it more complex on the other.

In regards to Workspace One, I’m actually very excited to watch the evolution of A2, which will be delivering AppStacks directly to physical Windows 10 endpoints, likely via AirWatch. As a former veteran Microsoft SCCM (ConfigMgr) engineer, delivering applications and controls on Windows devices that aren’t connected to the corporate network isn’t a new concept, it’s been possible by establishing a PKI for quite some time, albeit complex. What is new is the concept that with the improvements that the Windows 10 operating system has brought about, it’s now possible to manage policy and applications on Windows 10 devices natively with Unified Endpoint Management software, which can provide sandboxing technology. This sandboxing and isolation is a BYOD game changer and when combined with application delivery and seamless experience between different operating systems and devices can make a huge difference and reduce the BS logon and auth time in-between actual work. It’s my personal opinion  that we’ll see a real uptick in uptick in UEM combined with Digital Workspace transformation the next 3 years.

Until next time my friends, I hope to see you all on the battlefield of fighting for the users.

Posted in Uncategorized

Horizon View 6.2 – Cannot Disable Connection Server – Failed to update Connection Server

Recently saw an error message when trying to disable the connection server via the admin UI, which reads:

Failed to update the Connection Server.

Images taken from a twitter post by Ronald Westerhout @rwesterhout81

Untitled

So it turns out from Ronald that unless you have both the SSL gateway and Blast gateway either checked OR unchecked the disable button won’t work. Not sure in what versions of View this problem exists, because I’m pretty much only disabling connection servers when there’s a problem or when doing an upgrade. Either it’s a bug, or a KB needs to be built for this error dialog. Until then, I hope this post finds you well fellow Horizon administrators!

Capture

 

Posted in Uncategorized
Papers
People
Map

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 31 other followers