 Hello, Grant. How are you doing? Hey, pretty good. How are you? Well, I'm doing fine and Thanks for having this conversation with me. It's really great to have members of the OpenShift team talking with me and sharing all your opinions and experiences about OpenShift and OpenSource as a whole and I would like to start like asking you like well about you if you can introduce yourself and tell us a little bit about you And you work at OpenShift. Okay. Sure. Yeah, so I've been on the OpenShift team at Red Hat Since probably about day one So roughly four years something like that back before it was even an official project or product before we had anything built it up from scratch And before that I was a Principal software engineer at Red Hat. I'm from the engineering side, IT side of the house Okay, and currently what is your focus inside OpenShift? Yeah, so right now I Like to think of myself as a man with many hats So I'm a developer advocate or evangelist I also manage all of our evangelists and I also Work a lot on marketing believe it or not to developers so technical marketing Okay, great This year it seems that the interactivity around the OpenShift road show was really heavy Do we were having presentations in many cities? Would you like to share some of that? Yeah, so that's kind of interesting. We just had this idea one day on our team mailing list to You know go around two different cities throughout the country and you know Highlight the new OpenShift release that we had which was OpenShift 3 which was a complete re-platform re-architecture of the system and we started with like five or six cities in mind and you know, we put together some justification for going to these Cities and once we said we were going to these you know first six cities or so The demand was absolutely insane people wanting them in their own location So we ended up I think last time I counted was like 30 some cities that we ended up Going to over a three month span. So it was pretty busy Each of the locations we tried to do somewhere fun For instance, I was in I think it was Minneapolis one of the first ones we did the Baseball stadium there and so we had the the road show event Where people could try out OpenShift at the stadium and then we all stayed and watched the game afterwards We've also done them at Tech centers and even bars and breweries before So it's been pretty great, you know each city I think we if we could fit 50 people in we would normally get 150 to 200 people wanting to actually sign up and go Which was just crazy and you know, it was a lot of work because we'd have to add cities on the fly We'd have to add additional dates. I think we're up to our third date in Washington, DC now for example Okay, well, so I'm imagining that perhaps next year we're going to have another road show. Yeah We're talking about it planning now A lot of people have been asking us to continue the trend to to bring these, you know pure tech Focused days to their location. So we're planning on, you know, what content and where we should go early next year So you mentioned OpenShift 3 So and that it was important for the road show to tell people about developers about OpenShift 3 What was it so important about OpenShift 3? What was the change the important change that you had between OpenShift 2 and OpenShift 3? Yeah, so the big deal with OpenShift 3 is OpenShift has been around for many years And a lot of other platform as a service offerings have been as well, but they've all kind of been based on their own implementation of Linux containers whether that's LXC or you know with OpenShift we Created our own Linux container based on SeLinux Linux control groups and PAM namespaces for poly and statiated directories But what we had seen over the last couple of years is this trend towards standardized container formats and the OpenShift team and Red Hat Realized several years ago that perhaps Docker was going to be the next big thing and so we bet very early on on Docker Quite honestly before a lot of people I even heard about it We recognized that it was going to be a great technology for developers and for running Platforms at scale and so what we decided to do was kind of step back a little bit and just take a break From the current platform as a service trends and really think about what we need to do To go beyond platform as a service and to create the next thing in IT That's really going to be beneficial that evolved out of platform as a service And so we changed our entire development model on OpenShift 3 and that initially I would say for the first year year and a half And we weren't very public about this we did most of our work in the Docker ecosystem itself and Contributed just tons of code up to that upstream repository to get it to a state to where we felt comfortable as a Product and as a company to be able to support production workloads running on Docker containers And I believe at the end of the day Because of all that work we ended up and still are the the number two Contributor to Docker and so we took this Docker container format And we wanted to make it relatively available to developers to use the doctors pretty easy to use as a Developer on your local machine, but where things get pretty complicated is when you want to run your applications or your containers as scale and I'm not talking about massive scale Even though that's part of the benefits of the OpenShift platform But even just running two or three containers load balance with HAProxy or whatever the case may be that gets pretty complicated pretty quickly for developers and so once we had Implemented the the Docker stuff inside of the next version of OpenShift. We then realized that to have Production class applications. It's more than just the container image format and so we identified another project at that time called Kubernetes which quite honestly no one had heard about when when we got invested in that and we worked heavily on the Kubernetes project with Google and We're also the number two contributor to that project And so those two things are important both Docker and Kubernetes because it's it's good to know that as a team OpenShift and as a company we Bet on those technologies way in advance. We're talking years ago to make them viable and so the reason we needed Kubernetes if you're not familiar with it is to do orchestration and scheduling of your containers and so what happens is your Docker container Actually runs in this concept called a Kubernetes pod and they can easily scale those pods up create replicas of them And let the underlying platform decide which server that you're going to deploy that new pod or new container on and then orchestrate and all of the services load balance Whatever the case may be across all of your pods whether they reside on, you know, 510 or a thousand different servers And so once we got Docker and Kubernetes working, I know this is a very long answer But we realized that Kubernetes and Docker are great But they're not very accessible for the average developer So think about you know your non startup non hipster developer That's kind of behind the bleeding edge curve They want technologies to be trusted just a little bit more before they start working on them We realized that the tool sets provided Like I said, we just wasn't very accessible to developers They had to learn a lot of new Technologies and so what we added on top of Docker and Kubernetes is this workflow for both developers and systems administrators to be able to take advantage of containers and running containers task scale and production or in any environment honestly and Let developers work that they let developers work how they work today whether that's inside of their IDE Or on the command line or via a web browser To let them just focus on their code and not have to worry about the sysadmin aspects of it And then to let sysadmin's allow developers to self-service Creating these containers and these pods I'm with with restrictions obviously and so, you know, that's why OpenShift 3 is it's a complete rewrite a re architecture Replatform every single line of code is different We didn't really maintain anything other than core concepts that we wanted to to come over into the new system Well, actually It was quite detailed and I think the viewers are going to appreciate that your point of view on that and but now You talk all about that about OpenShift 3 and even before the entire road showed was over OpenShift 3.1 was already announced It seems that you basically have to keep adapting to everything that is there and that the entire pipeline is really fast It's changing. So what what can we expect to have with OpenShift 3.1? Yeah, so OpenShift 3.1 just furthers shows our commitment to the platform and the keeping Working on it to move it forward to provide great features that people want Some of my favorite features in OpenShift 3.1 as a developer because that's my background. That's my history That's what I do is the ability to Do just some great things inside of the web console itself So you can look at aggregated logs across all of your containers and have them streamed in the web console Via web socket connection. It's very cool So you don't have to like fire up your command line and log into pods and tell files and all that stuff You just with a single click from the pod you can look at the log files. We also have this topology visualization tool, right and so if you have an Application deployed on the OpenShift platform and let's say that application consists of you know five front-end Containers that surf scene your you know your web UI whether that's JavaScript, Node.js or whatever the case may be and then that talks to a set of microservices or Some back-end services that's deployed across three different containers and then all that's talking to a replicated Mongo database across five containers and it's all front-end with the HA proxy load balancer Well that you know when you start talking about real applications like this it gets very complicated and To understand all of the touchpoints and integrations between these two containers And so we developed this tool that'll you know You just click a button inside the web UI and it draws this map of your application and shows all of the pods and how the Communication happens between how the traffic flows Out through the external route down into the database and so that allows you to quickly You know visualize the topology of your application another one of my favorite features is the available the ability to open up a Shell or command line tool into a specific container right from inside of the web browser And so you don't have to and this is I Actually started using Windows 10 not long ago and Windows 10 was was kind of a pain for me to get set up as a You know Linux guy because I live and breathe by the command line And so, you know, I hate the command comm or cmd.exe or whatever it's called the default shell that ships with Windows because then you got install open ssh And you got it, you know generate keys and the terminal just sucks right and so What this allows to be able to open up a terminal inside of the web browser is just with a single click of the button as a Windows user I can completely ignore All of the stuff that I need to do whether that's installing putty or whatever the case may be to open up a exec Bash shell on the remote containers. I just click the button within, you know, half a second. I'm dropped to a shell Well, yeah, that's that's awesome So one last question for you and this one is quite open is what is like the future for OpenShift? What are your parting thoughts and what do you think like people should get like out of this conversation that we just had? Yeah, so I believe the future of OpenShift we're going to be focusing More on the developer experience and the user interface designs whether that's inside of the IDE or In the web UI or even great console tools or REST APIs To really continue down the path of making a container application platform like OpenShift is Accessible to as many developers as possible so they can have the benefits of running these new technologies without changing how they work On a day-to-day basis Okay well, thank you very much Grant for all your time and your questions and I do hope to have you here like Soon we're going to talk with other members of the team and and any time that you want to share your opinion about OpenShift OpenSource Red Hat as a whole or just software development. You're welcome. Okay. Cool. Thanks Diego appreciate it Thank you. Bye