Share: |


JohnVincent.jpg

This is the third excerpt from the podcast interview with John E Vincent in the on-going BMC DevOps Leadership Series. John makes a couple of important conceptual points in this excerpt IMO.

 

________

 

 

Tom Parish: OK, so let's look ahead, where do you see DevOps going over the next two to three years?

 

 

John Vincent:  I think the biggest thing is people are going to realize that DevOps is not about development and operations.

 

 

Tom Parish:  Yes. Despite the name.

 

 

John Vincent:  Yes, despite the name. It's a catchy name. It works.  And right now the biggest roadblock that organizations face is their interface with the operations team.  But as that gets smoothed out, I think the next big one you're going to run into is security.  Your SecOps team is going to have its own concerns.

 

 

And I think eventually people are going to realize the issue is not necessarily the interface between developer and operations, it is the interface between IT and the business.  And then trying to possibly realize the goals that sort of agile started in aligning IT with business. 

 

 

I think another one is that you're going to start seeing more hardware become programmable, exposing things that were APIs. And that's going to cut further the delay between provisioning and resources.  You know one of the things that people say “DevOps is sort of born in the Cloud” and there's a bit of truth to that in that when the artificial barrier to getting resources online is removed -- the one around six weeks provision and purchasing and all that -- there's no more excuse for saying, “I can't do this now.”  Well, yes, you can. It’s ready now.  You just need to get it ready.  So, people had to become more efficient.

 

 

And I think you have some companies that are coming up with programmable hardware, you've got people doing private Clouds that have programmable networking and that type of thing is going to expose even more inefficiencies that either automation or those kinds of practices will assault.

 

 

Tom Parish:  So what would be an example of that and it sounds like you were talking about something below -- along further down the stack?

 

 

John Vincent:  So, well yes, right now one of the benefits of an Amazon EC2 or, you know, installing open stack or Cloudstack to your private infrastructure is that you abstract out the configuration of the infrastructure.  There's an API on top of it.

 

 

Tom Parish:  Exactly.

 

 

JohnVincent:  But obviously people still have real hardware and in cases they have real network switches and they have real routers and firewalls.

 

 

Tom Parish:  You bet.

 

 

John Vincent:  So what we’re talking about now is there are vendors coming out with modified versions of the traditional networking hardware that is programmable over an API.  So now you can write code to actually make those changes as opposed to a manual, go in and configure and sync, kind of situation.

 

 

The same kind of evolution you see with the servers and infrastructure as code.  I mean, we’re really moving – IT is a whole – I feel like it’s going to go from the same kind of shift that was agrarian to industrial.

 

 

Tom Parish:  OK, very interesting metaphor, never thought about it quite like that. So that sort of further accelerates the opportunity for being agile and quicker in the way that you would…

 

 

John Vincent:  Right. It’s the efficiency thing.

 

________________

 

The next excerpt from John's interview is coming up.