 This is Jason Porter with the Red Hat Developers Program, here with Eric Chabelle. How you doing Eric? Very good man. Nice to see you again. Yeah, it's good. It's been a while. It's been a while. So what are you working on today? Today. Or not necessarily today, but just in general. I know in the past you've done a lot of BRMS stuff. Yeah. My role within Red Hat is to change a little bit. I spent about four years doing the middleware stuff, evangelizing a lot of the BRMS and the BPM product line. I've now moved across the fence, so to speak, into the platform space and the cloud space, and we now have a complete full stack demo. So across virtualization, open stack platform, everything resting on the OpenShift container platform. That's all running on OpenShift. Is that a demo that people can go and download and try out? You can go over and check it out at the stand right over there. Okay. Great. What about after Summit? After Summit, I'm going to do a session here in your booth in just a second to show how to install the OpenShift container platform in about three or four minutes on this Wi-Fi. Excellent. This is all available online on the Red Hat demo central. It's a GitHub organization. There's a bunch of stuff in there you can play with on top of the cloud, all for free. Oh, great. Even better. Very nice. What is it that developers need to know about the full stack running on OpenShift? If they would like to take a look and Google around a little bit, I wrote an article that gained quite a bit of traction. It starts with my transition into this role as an app dev guy. In the past, you're pretty much not interested in what's going on in the stack. I really don't care. I don't want to know. No, I'm writing an application. I want to focus on the app. I don't care about underneath. Exactly. And everything we do at Red Hat in the developer space is trying to foster that as much as possible, of course. You want to focus on what you're doing. That's what containers are bringing to the market. It's focusing what you're doing, containerize it and hand it off or move it along down the chain. You used to do that with your middleware applications and the problem was the first dump of an error confused everybody but the guy that wrote it. That's kind of the stuff you want to put into a container so if the container doesn't work, you can hand the container back and do your thing. My focus has been to bring this stuff over and when you look at the stack, you can't ignore the stack anymore. You have to understand a little bit about what's going on in the clouds, what the differences are, what containers do, what this means. How deep do I need to get into understanding the stack? Do I need to go all the way down to the OS level or the hardware level? Obviously, OpenShift is going to abstract away some of those details from you. How deep do I need to go? When I say something like this, it's taking the amount of time to step back and look at an architecture in your organization and understand what virtualization means, understanding what programmable infrastructure means, understanding what going to the cloud means. All this ties together into the hyper-cloud story of Red Hat, right? You cannot ignore that. Of course, you have containers at your daily job right in front of your nose, but when you're deploying these on one platform to another platform to another platform, it's kind of a good idea to understand what is going on in those environments. There's no need to completely ignore that anymore. You can't just say, not my problem. It's bringing a lot more interesting stuff, I think, to our developer roles. The tooling is basically rising up because when you're putting a container together, what used to be the hardware machine in the data center? Let's be honest. Some of the tools around that kind of stuff, they're kind of handy for your debugging, include operational kind of stuff. It's much more localized. We do everything we can to keep that stuff either in the cloud for you or locally, just on your machine, tied into your IDEs and tied into different management things. One of the workshops I'm giving this week at the Boston Jug is going to be showcasing playing as a lead developer, setting up a demo environment that includes six containerized services, some of our products, all the stuff on the OpenShift container platform. It only takes about half hour. It's very much a realistic experience of putting together a development environment for your team. Excellent. You mentioned hybrid cloud. How difficult is it for something I have on OpenShift to talk to maybe a data center that I've got where we have some other applications or some other data? In what way? I don't understand. Talk to a data center? Let's say I've got my main application is deployed out on OpenShift, but I've got an extra data store that for whatever reason they want behind a VPN. How easy is it for my application to talk to something behind a firewall or a VPN? That kind of depends upon how you're architecting your environment. I don't really see the clear answer you're looking for. It's a little bit of a tricky one there. I guess a lot of that depends on the architecture and everything else that plays into it. Are you tying this together with service communication? Is it headless? Is it microservices? How are you bridging these environments? What are you doing? What are all the questions to answer during the architecture phase? A little bit of that can be encompassed in something we put in the cloud suite where we talk about managing highly scalable application deployments. With your containers you think I have a container. Once I get that up and loaded into my environment it's just a copy to create more of them. But you also have to manage this across a worldwide scale. We have a couple of customers, one in Europe for example showcased in a lot of the slides I use. There's a financial institution that has three data centers around the world and you have to put policies and things in place through things like cloud forms using Ansible, being able to script some of this stuff to trigger things to watch for... let's take Germany for example where you're not allowed to export privacy information so if you're using government apps and things like that they have to run in country. So you can say Amazon, that's nice or you can say Google, that's nice they don't want to localize. So you have a policy now that this app, this container this deployment needs to be localized to this region. So it has for example just one option, one data center. Another demo I talked to about this is when you're migrating and dealing with three data centers for example one is certified hardware and some of my applications require certified hardware. One of our customers is an Amazon like thing in the Netherlands that runs only on certified hardware and not get support if you're not running on the correct JVOS That becomes very difficult in a public cloud environment but less so in a hybrid class So you can have your own private section where you say okay this needs to run these apps you might have something along the lines where the persistence storage stuff that you roll out needs to be close enough to get the speed performance you need to look up data the caching needs to be closer things like that Very good and one last question for you What would you say is the number one thing that developers need to know or understand about OpenShift? Get started today The sooner the better I've been on it since we acquired the company before it was even OpenShift If you have not gotten involved with this container platform you are missing a whole lot of fun It's it's the future It takes so much pain away It's not even funny You can run it locally You can experience it online It ties into all the developer tooling you're used to especially the middleware guys There's just really no excuse not to be doing it Who wants to mess around with configuring stuff on your local machine anymore Very good We just released OpenShift.io You can go check that out and sign up It's open to the public although it's available based on resources They haven't opened it up yet If you're not on that list already go check out OpenShift.io and take a look at that Thanks Eric