 Hello everybody, welcome back another technical demo around the core of the application. My name is Daniel Lowe. Today I'm going to showcase around the running forex cluster with the Quick Starts on developer sandbox. So what is the developer sandbox? The developer sandbox fundamentally provides developers with a probably open space environment in a shared and multi-tenant open space cluster, which is a pre-configured server developer tool. For example, CoreLady workspace is web IDE application environment environment, and the developer can easily create containers from their source code from gimme property or even .cofile, as I read, build a new application using sample application with the stacks provided. And developer can also add services such as the database from existing of which the template catalog, what you probably have charted, and there are so many benefit from a developer sandbox. It's a free cluster that the developer only needed to do is sign up the Red Hat developer website. So let's get started. So here you can access the developer sandbox using Red Hat's link in the slash def dash sandbox. When you access the developer sandbox, you need to first sign up a free credential developer at Red Hat.com website. And after that, you can just log in with your credential, and then at the time your developer sandbox cluster will be speeded up in the next five minutes. So once you enter the developer sandbox and go to open the developers console, you can find the multi pool in the videos. You can find the various quick start, how to get started, your application development, and deploy a specific solution with the up push to container platform. So here is a new corpus quick start here. So get started with the corpus using ham chart and getting started with the corpus using asus to immediate build. And then you could already find another existing one, the corpus application binding. The corpus quick start is to bind your corpus application to streaming, once you change the FG cap card. So today I'm going to go through two quick start brand new ones, like get started with the ham chart and S2I build. Okay, let's get into the demo. Okay, first of all, as I already mentioned earlier, let's do access the URL, red hat slash def dash sandbox. Once you access the URL, you can find all detail of what is sandbox and there are some practice, how to use that and what kind of benefit you can have as a developer. And then click on get started. The sandbox I already sign up. So after you sign up, you just click on start your sandbox. And then it redirect to a login page with the single sign on just click on developer sandbox. So you log in, open shift the cluster and then you can just go to quick start to click and then find the corpus related quick start here. And then there are three quick starts already built in your developer sandbox. So let's try to get started with the corpus using S2I build. As you see, there are six steps to finish this quick start enablement. And then also you can find what kind of benefit you can have with the corpus application development, like a container first and unified configuration. Let's try to click on the first step, create a new corpus application. The first step is click on the perspective switcher, like a developer standpoint and click on add menu and then you can find multiple perspective you can get starting like a sample application from get you part of it or depth file, et cetera. With the developer sandbox, you already have two names faces like your username dash depth, username dash stages. So you don't need to create a new one. It's already limited resources for you. So we just use depth namespace. Click on give to improve your application. Here's a sample example corpus application with a quick start and the container directory is getting started. You can actually add any other give you part to your want. But just follow this quick start just using an existing example. You can put in the more computation here for example has check or resources limit. So once you click on has check, you can add your ridges and write this problem. Once you click on create the button, the corpus cannibal icon just shows up which means your corpus application got started to deploy or push the cluster with this user namespaces. And then you just check your world. So do you see the corpus application and do you see corpus deployment, et cetera. You can just make sure everything is working along with the quick start instruction. So click on the icon. You can find the deployment, et cetera. So go to the next step, just a few view states. Once you click on the build icon and you can find the load detail, how build is working and click on the last thing is to check your world. So you have to see the company status in the build load. It takes maybe a few seconds or a few minutes to complete the all build strategy. So during the build, the build process, you're getting part in the main room packaging build and then containerize the application and push it into internal container registry. Okay, so move on to the next step. Just a few associated part to it to what kind of application is implemented. But the one of the beauty of the sandbox, we already installed the Core-Ready workspace for your application development environment. So when you click on the Core-Ready workspace icon, it will bring you to Core-Ready workspace directly instead of go to get it properly. Which means the developer can edit your application for itself and deploy it back to the container platform right away. So it's one of the beauty of the developer sandbox for the developer. And once you develop the application deployed to the back and forth, just like the cloud will develop in-bound. So just take a look at that. The guest started a project. You can find the hello and greeting endpoint. And here is the CDI injection when you pass down a parameter and it will return with a hello, something like output. Next step, build part status. In the new hover, your part icon, you can find the running status and we just success to part deployment. And then the next step and the number five, the change the deployment icon with the purpose. The default is the Java icon. So this application based on the purpose framework. So we need to make sure this part based on the purpose. In order to that, just delete the existing label and then the new label at the output.io slash one time equal purpose. So there are already predefined icon to differentiate your multiple part in the same namespace. So now you can see the beautiful purpose icon on your part. And the next step to make sure everything is verified you're working. And then the last step, we want to make sure application functionality is working using URL and the endpoint, one of endpoint hello, which will be return hello. And another endpoint is hello. They're supporting with some formula like my name is Daniel. And then you can find that the return is a hello Daniel. It's a pre-working. So just a six step how to get started the focus application development using developer sandbox as well as already of space. So it takes just five minutes to learn how focus works in developer sandbox. Let's try to do another quick start. So once again, just for fun. Okay. This is starting with the course using handshark. So handshark is one of the popular to manage the configuration and runtime environment on Kubernetes cluster. So luckily we have handshark already included in developer sandbox. For the most team perspective, they can define the standard course application runtime environment from developer sandbox. Okay. So click on hand chart and just search for focus and just create this hand chart to install. And you can change the configuration from the GUI view or the YAML view, whatever you can select your preferred way. And then just click on hand chart. So there are a lot of configuration, but we just use the default configuration along with this instruction and check your world to verify you're working. So as you see, you can find your new focus application and you click on the detail. Maybe you can find the image pool backup, but don't worry about that. So click on hand chart to release UI. You can find the notification here. You might have some image pool error or image pool backup error because the build is still undergoing. So next step, you're going to check it out your build process status. Go to build log just like we did in the previous focus S2Y quick start and you can find all detailed logs here and the ones to push its success. And then your focus application is now running on developer sandbox opportunity cluster. So I think it's a week done in the step two and then I just click on yes, everything is okay. And the next step, go back to topology build and the focus department is working. I just checked it out once already and then click on yes and then go to next and the last step, just check all application functionality using a lot of URL and then go to hello. This application, you can see you're getting started application examples. So go to building, like for example, hand, hello hand. Okay, so today we're going to run about focus application development using quick start, which he provided in developer sandbox. So now developer just sign up freely in the developer sandbox at developers at redhead.com and then they can enter developer sandbox and go through a quick start how to develop focus application using S2Y reload from your gateway property and you can actually use existing sample application but also a little more operation team perspective or even devos team perspective you can set it on your standard focus runtime environment using ham chart how to do that using quick start instruction. Thank you for watching. If you have a more interesting question around the quick start with the focus and developer sandbox, please let us know. We are more than happy to address your question right away. Thanks again. Have a good rest of the day.