 Hi, my name is Steve Speicher from the OpenShift team. I'm going to talk to you today a bit about some of the upcoming features in OpenShift. I'm going to show them to you with the open source community origin bits, what's coming in a 1.3 release, which will eventually make their way into Red Hat products. OpenShift dedicated container platform and online. Hopefully things are subject to change. The way I'm going to do this, I'm going to paint a couple scenarios as a couple different personas or people. First, I'm going to start out as this employee who's new to a team. The team's been working with Java, Node.js, have been playing around with microservices, but I've come from a background of .NET, and I want to get familiar with this OpenShift thing that they're playing with. I learned about, hey, there's this cool online developer preview where you can sign up and easily get started. I'm going to do that. I've logged on. My name is Joe Coder. I'm going to come up with some playground to mess around with. This is pretty simple. I'm going to create a project. There's all kinds of technologies. I wanted to toy with. I've got some Instant Apps, some Java, some PHP Ruby. I know some of the people who are working with are talking about Node.js and Mongo. Let me see what they've got for Node.js. There's Node.js 4. I'll just go ahead and grab this. Give it some name. I'll say that's my web app. That sounds good. I'll play around with the example they've given to me. Okay, this sounds good. Let's just create this application. Okay, so I see I can manage my app. I can get some command line tools. For now, I'm just going to play around with the online bits through the web browser. Let me continue here. Okay, great. I see some things are growing on here. My web app that I created, it looks like a build is running. If I wanted to, I could click on that. I see some logs here. I love logs. It looks like it pulled down all the dependencies. It's already pushing the image back up that it had been built, it looks like, and it's almost done. Let me go back to the overview and see what I've done. Health checks. Sounds important. I'll check back on that later. But now I just want to get something going in my playground. So no deployments. I have no group services. Okay, I see our deployments now kicking off because the build completed. Great. I do remember that I wanted to connect the database to this. And then I mentioned there was Mongo was commonly used. So I'll come over here and I'll ping a friend and say, hey, you know, I'm new to the team. What do you recommend? And, you know, oddly enough, they just give me this big blob of, of JSON to play around with and say I can just import it. And like, I'm not sure what that really means, but I can see here that I have an import YAML JSON. I would have expected it checked in the source control some point, but I won't get on my friend for that right now. So I'll flip over. I'll take a look at what they gave me. I'll grab the Mongo database. Templates and well, I'm glad he gave me that file because I probably would have struggled a little bit typing all this in. Maybe there was something back here in this catalog, but I trust my new coworker. I probably should use what they gave me. Yeah, I probably want to apply it and just use the results of that template. So any parameters, typical developer, I take all the defaults and come back overview. Okay, cool. So I see my web app has been running. The build had completed a little bit ago, and now I starting to see some metrics that are involved with this. So I'm going to hand this out to a couple of friends as I'm hacking on. I might want to make sure that there's some high availability. So if my application goes down and the time it takes to come back up that people aren't experiencing any downtime. So let me go ahead and scale this up to have some backup services there. So I see now my Mongo database is firing up. Well, that's good. So since I'm using this Node.js front end to this back and I'm going ahead and group this service together. So let me do that. Go here, grab the Mongo. That's nice. It tighties it up a bit. It allows me to see them together, link together as I think of them logically of how I use my Node.js front end to consume my MongoDB back end. Well, okay, so I guess I'm familiar with the platform now. I would like to play around with a couple of things. So one is like, I know the technology better that I have, but I didn't really look for .NET. Well, I see there's some .NET stuff here. That's cool. Let's just give it a simple name. I'll try the sample that comes with it. Again, some guidance and I'll flip back over to the overview to see what's going on. See it builds running already. I can jump over and see the logs. I can file the logs and I'm used to seeing all this where it's pulling some dependencies and now getting ready to perform the build. So this is familiar territory to me as well. So all this is good. So it was easy for me to get going with Node.js. I'm now able to use the technology that I'm familiar with, .NET stuff, and start playing around with this as well. So good. As that's going along building, I had skipped something before when I was looking at this and I wasn't sure what the point image was. So I remember in my previous job, I used to use this other Docker image from Docker Hub. But wait a minute. If I'm looking for this, it's telling me that it's actually run as a root user. It seems like that's pretty important that I know about this and I don't want to cause any issues in my new job here. So I'm going to just back out of here and I'll probably go with just the ones that I've been told I should use or have been approved for usage. So there you go. I've easily been able to walk through this without much in the way of assistance, figure out how I deploy an application. I kind of both the web front end, the database and also some other technology I'm familiar with in the .NET, leveraging direct access to Docker Hub as well as access to raw files in the backend as well. And again, I could say I'm going to leverage the same backend database service and I could link it up to that service and now I have kind of a consistent view of what my app is, the front end, which is the .NET MongoDB in the backend and have a clean console on how I view those things. So that was Joe Coder getting started with OpenShift 3.3 Upcoming Release, so an early preview of those features.