 Well, hello everybody and welcome again to another OpenShift Commons briefing. This time I'm really thrilled to have with us the gang, the entire crew, from click to cloud. Capel is going to be driving the conversation. What we're going to be talking about something that this Linux person doesn't always talk about all the time. We're going to talk about Microsoft Visual Studio and deploying and building .NET applications to run on Red Hat OpenShift in the new world of Docker and containers and this is the team that's making it all possible. So I'm going to give them, they've got a lot to talk about, I'm going to give them, hand it over right away to Capel and Capel if you can introduce yourself and tell us a little bit about click to cloud and then run through your demo. Then afterwards, if he's finished, you can ask questions in the chat during the presentation but we'll answer any of the questions afterwards and open it up for conversation. So there you go, Capel. Get started. Yeah. Thanks. Thanks, Diane. Hello, everyone. My name is Kapil Thakkar and I'm a senior system engineer here at click to cloud and we're focusing on Obership 3 and containerized area and I'm here with my team mates Pratika Madan who will be contributing via chat and help answering you questions. So click to cloud is totally focusing on the OpenShift and the Docker technologies and it's an ISP partner of Red Hat and the Gold Partner of Microsoft. So topic for the day. So today we are going to talk about the integration of dotnet applications with OpenShift 3 and we will see how we can use the click to cloud OpenShift tool for Visual Studio. So click to cloud OpenShift tool is our devop solution which allows developers to build, manage and deploy their containerized dotnet applications and actually a lot more other applications straight from Visual Studio ID to Red Hat OpenShift 3 cloud. So I want to start here with a quick statement problem of Visual Studio developers. So the first problem we see here is currently there is no devop solution available for Visual Studio developers using which they can build, manage and deploy their application right from the Visual Studio ID to OpenShift cloud. And other problems we see here that is there's no source to our images and dotnet applications and templates directly available in OpenShift 3 cloud. Suppose a developer wants to host their dotnet based application on OpenShift 3 platform they have to design a Docker file based on their application needs and deploy their application using OpenShift 3 command line tool. So to fix our first problem we worked with Visual Studio developers and came across with Visual Studio extension for Red Hat OpenShift 3 cloud and it helps Visual Studio developers to create applications right from ID and deployed on to the OpenShift 3 cloud. Along with this to enable dotnet support on OpenShift 3 we have developed dotnet source to our images and templates that minimize dotnet developer overwrite to create Docker file and create application from the command prompt. So you can directly download the dotnet source to our images and templates from the Docker app and the GitHub URL. And here we can see the core architecture of our solutions. So here we can see the Visual Studio user creates a new application using the OC3 Visual Studio tool by providing source code URL and the GitHub and from the GitHub and select the templates from the options. So the Visual Studio OpenShift tool requests OpenShift to create new application based on user input and OpenShift merge the source code with the builder image provided in the template and creates new image using the OpenShift source to our engine and it will create the ASP core 1.0 application on the OpenShift 6 cloud. Let's getting started with the prerequisites to run the application you require the Visual Studio 2015 installed on your Windows machine. So currently the current version is compatible with any additions of the Visual Studio 2015 and next you need the Git version controller and the OpenShift 3 binaries for Windows which is OC binaries and also require the dotnet images and templates if you wish to enable the dotnet capabilities on OpenShift 3 cloud. So you can get the detailed information on dotnet source 2 images and templates for OpenShift 3.0 right from the GitHub URL. Now we can see to get Visual Studio extension for OpenShift you can directly go to the Microsoft Visual Studio Gallery and you can search for the keywords click to cloud or OpenShift from there you can select the appropriate plugin version of OpenShift Enterprise or the original one. So you need you can download the extension from there and once the extension is complete you need to activate the trial period by completing the registration process and verifying your email address. So we'll show you the Visual Studio Gallery first where the extension is available and here we see and here we see the extension is on Microsoft Visual Studio Gallery and you can directly download it from here and also you can get the user guide which shows the registration process and the back links of the pre-quested which is required to run the OpenShift extension. So once we are done with the pre-quested installation we are ready to create our first application on OpenShift Cloud. So I'm on my Visual Studio and yeah. So I already downloaded the click to cloud extension on my machine and you can see the click to cloud menu on top of the menu bar from here we can create a new application on OpenShift Server also we'll talk about the modifying the existing application and also we can see the OpenShift Explorer and its features. So OpenShift Explorer is a gateway which enhance our capabilities to work on OpenShift Cloud. So let's create our new application first. Here we need to provide the server URL, the OpenShift server URL and your username and your password then click on next. So once you log into the OpenShift server it will ask you to create your first project if you do not have. So I'm going to create my first project and click on finish. So once you have created your first project you can see the list of projects available from the top down and here we can see the list of templates available on the OpenShift 3 server. So we can create application using the existing template available on the OpenShift server or we can use the custom template available on my local machine. So I'm going to use the OpenShift server templates. So as we can see the ASP.NET template and the ASP core template I have already deployed on my OpenShift server. So now currently the application which I'm going to create that the sample application it provides the MongoDB services and ASP.NET, ASP core front end. So I'm going to select the ASP core MongoDB template here. By selecting this template I can also see the resources which are going to be created along with this application. Like here we can see the image streams and service nodes. Click on next. From template parameters screen we can provide the template parameters like the MongoDB username, the database, the password. So I'm just going to provide the database password. So I'm going to use the name for user. Also I'm going to provide my github source code URS here to deploy my source code to this application and click on next. From resource labels you can provide the resource labels. So I will go to the default values here. Once you click on finish it will start creating your application on the OpenShift server and it will display the application summaries which highlights the resources which is going to be created and the parameter values here. So you can also get the web book URL directly from here which helps developers to automatically trigger the build right from the github repository to your OpenShift application. Click on OK. And after that it will ask you to clone your application to your local server. So I'm going to write the clone destination path here. Yes we have. OK and click on finish. So it will start cloning your application from the github repository and once the cloning is complete it will launch the source code. Yeah. Once the cloning is complete it will launch the source code to the solution explorer. OK. So here we can see the source code which I'm going to use in the ASPY.NET code application. And also you can see the build logs has started. You can directly see the build logs and it downloads the nugget packages for the application. So let's see the view page here. Yeah. So here you can see the source code and the view page which is going to be created. I am using the restaurant app application here which gives some tables of restaurant app ID in MongoDB. And here we can see the title and heading page. So this application will take some time to build and to complete the build. So till then we will see the existing application which I've created earlier using the same source code. Yeah. Here is the sample ASPY.NET code with MongoDB. So the same application I have created earlier with the same source code and MongoDB services. So let's see how it looks like. So here you can see the ASPY.NET code and MongoDB application running on my OpenShift 3 server. And this is the database connected. Let's write some data here. And here we can see I'm able to push the data from ASPY.NET application to my MongoDB. So the connectivity between the ASPY container, ASPY.NET code container and MongoDB container is working fine here. So once our build is complete, the application looks like the same here. We'll come back again once that will complete. So till then we will modify an existing application and we'll see how it looks like. So to modify an existing application, you can directly go to the street throughout menu. And here we can get the open existing application option here. So from here you can log in. So I'm going to clone my application, which I'm going to modify. So I have created an application that is ASPY.NET 4.5 with MySQL database earlier. So let's clone this application and we'll modify the some title here. Again, you need to provide the git clone destination. 2.5, okay, and click finish. That's again cloning the same. Yeah. So here we can see my application is successfully cloned and it's launched the source code to my solution explorer. Now, yeah. Now I'm going to modify the title of this application. So the ASPY.NET with MySQL. So I'll show you the same with the web browser how it looks like for modification. Okay. Here you can see. So earlier I have created ASPY.NET application with MySQL support on OpenShift server. And you can see some records I added earlier. So let's modify this title from the Visual Studio and push it to the OpenShift server. So here's the title. So I'm going to modify it. And just commit your changes to the GitHub repository directly from your Visual Studio Gallery and some uncommitted push. So once the changes is committed to the GitHub repository, we'll start the build directly from my OpenShift Explorer. Yeah. So here we can see the start build. So the start build will deploy the changes from my GitHub repository to my OpenShift server application. Okay. So this will take some time to complete the build. So till then we will see the build logs directly from here. Yeah. You can see the second build is running right now. And we can also check the build logs. So basically it's very helpful for the developers to trace the build logs and troubleshoot the problems. So it's committing the container and providing some, yeah, creating the user there. And load on the application. Yeah. Here we can see it's pushing the changes to my, yeah, successfully pushed. Now let's check the changes has deployed. Yeah. From Browse and here we come to Browse. Okay. It will take a minute as it's creating another pod. Like just a push it and you can see it from here. Okay. The pod build is complete and it's running push and gain. And here we can see we have modified the title of the application directly from the Visual Studio ID. Now, let's check our previous application which we have created earlier. Yeah. It's also completed. So let's see how it looks like. And here we can see the application which I've created on the start of this demonstration. That is ASP.NET COVID-19 successfully built. And let's add some data again here. And submit. And we can see it's working fine. So now let's talk about the OpenShift Explorer features. So far we have seen the OpenShift Explorer features like start build, open the application from browser from web browser and the build logs. So OpenShift supports a lot more features here like the port forwarding, the open terminal, the web book trigger. So we'll see these features one by one. Okay. So yeah. So suppose this is my application and from here I can get the web book URL from Visual Studio ID. So it helps the developers to deploy the, sorry, it helps the developers to automatically trigger your build while making any changes to your GitHub repositories to your OpenShift application. And in my scenario, actually I have not configured this web book URL to my GitHub repository. So I have started the build manually. And apart from this, we can also see the next feature that is, we can also see the port logs of the running container like the port logs here. And we can see, yeah, the listening on the address and so on. And the next is we can see the open terminal option. So like I have no.js application and I need to see, I need to log in to the container and I need to run the Linux commands and the container and see what the source code is going on. So I can directly go to the container from the running port, right click on the running port and click on open terminal. So you can see I've logged into inside my container and I can see the source code path and the source code which is used inside the no.js application. Now let's come back, exit and exit. Next is we can also edit the JSON files from directly from your widgets to the ID. So suppose I need to scale up my port. So currently I have a single port running here as you can see and I need to scale up port by editing the JSON file, the replication controller JSON file. So I will directly go to the replication controller and click on edit. And here I can see the replicas. I will go and change the replicas to two and save. Set and refresh it. And here we can see the no.js port. The two ports are running the one and the two. And the next is the port forwarding. So basically port forwarding helps user to access the application directly from the local host. So suppose I have created an application using the front end and the back end and I don't want to expose my database. I don't want to create a route for my database. And so my database will not accessible directly from my network to the cluster IP. So what I will do, I will start the port forwarding and I will access the database from the local host. So we'll see here. Suppose I have a MySQL database running here and this is my running port. So I will just start the port forwarding of MySQL database. And here you can see the port forwarding options and the local port and my remote port. I can also select the random ports which will be generated by the Visual Studio tool. And here you can see the other ports. I will go with the default port and start port forwarding. Yeah. And here you can see the port forwarding has started successfully. Now let's access this database from the local host. So I have a MySQL workbench here which I have used to connect the MySQL database. And I can show you the connection. Yeah, here you can see the local host host name, the database port, the username which I have used for this database and the database name. Just close it and connect database now. Okay. I've logged in from my database and let's check the tables. Yeah. Here we can see the table and the values. I will say we'll take the same values from the browser right now. Here and go to Routes and right click and show in the browser. So here you can see the same data available. So now I'm going to add some records from my database and we can see the reflection here. So I have a query. Okay. Let's insert something. Yeah. And execute the query. And I can see it successfully inserted the data. Again, check the data from database and click on execute. Yeah. I can see my record is successfully added and check the same from the browser. Yeah. Here we can see the reflection. So we see the port forwarding feature here and I have access to my database from using the port forwarding and local host. Let's close it and stop the port forwarding now. Okay. Yeah. Port forwarding and stop this port forwarding now. So there are many more features available on OpenShare Explorer. So for full feature specifications you can watch our YouTube videos at little cloud. And yeah. Now we'll come again to the PPPT. Okay. Yeah. So let's have a quick recall what we have to see until now. So we have seen the create.net application and modifying the existing application using the OpenShare tool. Also we talked about the OpenShare Explorer and its features like start build web of URL, view build and port logs and launching the terminal. Directly from the visual studio ID and we are added to the JSON file and created the replica of the board. And also we have seen the port forwarding feature. And here you can see the latest developments of OpenShare tool that is the OpenShare server adapter which helps user to directly publish the changes to the running container and it omits the build process from the OpenShare. Next is CD adapter which is also the latest development which helps user to run the CDK virtual machine on their development machine. And the next is the Docker Explorer. So you can also use the Docker Explorer to manage the Docker images to run the container directly to the Docker server. Now are these features in some next example. These are the feature plans in August releases that is support for asking in ASP.net images the remote debugging ASP.net application running in OpenShare container and compatible with older version of Visual Studio. So current version is compatible with Visual Studio 2015 any addition. But we are also working with make it compatible with Visual Studio 2012 and Visual Studio 2013 and the upcoming ones. And the next is the announcement in OpenShare Explorer 4 is to access the launch and okay that's all from my end. This is free to ask any questions if you have. Well thank you very much Kapil. One of the wonderful things about that that was there was no smoke and mirrors. It was all live demo and it all worked which was very amazing. My first question I think and anyone else who's got questions on can pop them into the chat is this is currently available for people to use now from the Visual Studio store, correct? Yeah correct. So they can directly download this extension from the Visual Studio gallery, yeah right from here. So just search for Click to Cloud or OpenShare keywords on Visual Studio market, sorry Visual Studio gallery and you can get the extension. Also yeah it's also available directly from the Visual Studio from tools, exchange updates and we can go to online and directly search for the Click to Cloud. So the developer can directly download it from here as well. Yeah it's searching right now. It's pretty awesome to see this actually working in production because I haven't used Visual Studio in a long time and I guess this week I'm gonna have to go back and reinstall it and start using it again. So it'll be lots of fun. So we have the, so any more questions? Not seen any questions. I think you did a very good job explaining everything. We'll have to get you back on in August sometime to give us the update when the new features come in and we'll post this recording on the blog.openshift.com blog site as soon as it's ready and people can download it and email you if they have any further questions. But it looks like a pretty robust solution for getting your .NET applications up and running on OpenShift 3 and we are very excited to get feedback on it from everybody out there in the community and we're looking forward to seeing you guys at Red Hat Summit and getting some of these demos done again in person. So if anyone has any questions, please send some emails to the Clip to Cloud guys or post them on the OpenShift Commons mailing list and you'll try and get them answered as quickly as possible. I know that Manesh is on and there are other folks on here. There's been a lot of work that's gone on in the background here. I'm not sure if Manesh, if you wanted to add anything in there. Thank you Diane and we'll surely be there in Red Hat Summit and we'll be definitely holding a session with you in the Birds of Feather meetup and there we can also, other people also can have, look and feel of our product and they can check how these two different technologies kind of work together harmoniously and we can create a heterogeneous cloud environment and we do not have to choose between Red Hat or Microsoft. It can work together. That's a promise. It's gonna be a brave new world out there because there are millions and millions of .NET developers and getting them to move over to containers and using it this way is gonna be quite interesting to see them all mixing it up with all the Linux folks. So I'm quite pleased with this new offering. So thank you very much again everybody for putting this presentation together and we'll talk to you all very shortly. Again next week and we'll be seeing everybody hopefully at the Red Hat Summit.