Hi and welcome to advanced application management with red hat open shift. My name is Mark Chernick. I am a senior curriculum developer at Red Hat. I am one of the developers of this course and I'll be the instructor for this course. So if you have taken some of our previous courses are previous courses were focused on kubernetes and on upstream kubernetes on how do we use kubernetes? How do we develop for kubernetes? This course focuses on red hat open shift. Right, so if you are familiar with our previous courses this course just like our previous courses comes with a handy pdf. Right and so this accompanying pdf comes with text right? With lectures and guided exercises and I would definitely encourage you to grab that pdf, download that pdf, go through that pdf because these videos contain maybe slightly different information or I do not read just from that pdf. Right and so let's take a look at what actually we're going to be doing within this course. Right, so we have our handy pdf at hand. Right and let's just take a very quick look at our at the contents of the pdf. We have our are in in the first chapter, right? We are going to be configuring our development environment, this course is focusing on on developer experience right? For our open shift for our open shift experience. And so we have to configure our development environment, that means configuring an IDE such as VS code. Configuring, get right, understanding what it is, how we use it. And we are going to use get extensively throughout this course right as well as VS code. Then we're going to take a look at how we can deploy some applications, right? We are going to be hands on right away and deploy some applications to write it open shift, right. We are going to take a deeper look at how we can customize these applications, right? So we have our source code of our application and we now know how to deploy it on red hat open shift. Right, how do we decouple that from our configuration right. By using something like secrets and configuration maps. And if you have taken our previous courses this might be slightly this might be slightly familiar to you but we'll take a look, we take a look into more depth, right? We will connect the application to database, right? And we will decouple the database configuration by using something like secrets, right? So this is our next chapter we are going to take a look at scalability, right? So we talk about cloud and cloud, you often hear about scalability and what it means to scale an application. Right, so we are going to explore that world and we are going to scale our application and even configure also scalability within red hat open shift. Right, we're going to take a look at how we troubleshoot an application, right? This is something that many users struggle with many developers struggle with, especially in the beginning it's very easy to make mistakes, make typos, right? Assume that something works in a way that it doesn't. So what we want to do is give you the tools to be able to troubleshoot your application, troubleshoot a failing built so that you know where to look in case your application does not behave in the way you want it. Right, so this is our fifth chapter, right? And last but definitely not least, right? We have our 6th chapter and in the 6th chapter, what what we want to do is essentially right, we don't do anything that we haven't done already but we are going to take a look at a deeper level at what we have done so far. Right, so we are going to take a look at the cli right? We are going to use the OC command line utility and we're going to use the OSI command line utility to peek behind the curtain just a little bit and see how some of the concepts that we have explored work under the surface. Right, so for example we are going to take a look at the kubernetes an open shift architecture, right? We are going to take a look at various resources right that we can use within kubernetes as well as open shift. Right, we are going to take a deeper look at the open shift routes. Right, and how the routing is done within red hat open shift, how source to image works, right, etc. And so this will hopefully give you more confidence in your ability to use red hat open shift as a developer and deploy your applications to open shift. Right, so what do we need to know in order to start? Well, this course was designed just like previously just like our previous courses with the bring your own developer workstation in mind, right. We support a number of operating systems you can use Linux windows as well as Mac OS operating systems. What I'm going to be using throughout this course is a Linux machine, right? We had red hat love Linux, so what I want you to do is take a look at the systems requirements, make sure that you fulfill at the very least minimum requirements. And hopefully they recommended requirements and better, right. One thing that I would like to notice is that we will need to install some applications, right? We will have to install git, right, we will use it extensively. And so you should be able to install some applications on your machine, right? No, Js is nice to have to install in case you want to try some of the applications before you deploy them to the cloud. Right, or to the open ship environment, whatever environment you will be using within this course I'm going to use the cloud environment but you can also deploy other environments as you want. Right and as I said we are going to be using the OC command line utility. Right and so we will have to install that one as well. Right, so at the very least these two applications we will have to install on our operating system. Right, so then we have our, some support system considerations right? This is just something that might confuse some people reading the pdf. The pdf contains guided exercises as well as lectures. Right, and so we try to provide the pdf in a form such that it is very precise, right? We write out commands that hopefully you can type out and execute. And so what might confuse you is for example that the bash prompt, right or well the terminal prompt rather than bash prompt might look different from the prompt in your system, right. So we are supporting multiple operating systems and the prompt that we use for our commands looks like this. Right, so this is the prompt that we choose to use or alternatively just like this. Right, just like this and so what is this prompt I'm talking about? Right, what what am I talking about? So let me open up my terminal application and so now in my terminal application and this is what I see. And right now you see a prompt, right? So a prompt is basically everything on the left. Before when I can type, right, so this is my prompt. And so my prompt consists of my user name, right? At my host name and then location brackets, right? And then I see that it is a non root shell, right? And then I can type my commands, right? However if you use something like a Windows machine you will have a different prompt. The problem will consist of something like PS which stands for Power Shell and then the location and angle brackets. Right, and then you can type out your command. And so the main thing that I wanted to say is that when you see our commands, especially in guided exercises do not be discouraged by a prompt like this. Right, the commands should work on all of the machines provided that you use Power Shell which is on Windows, which is the only supported shell on Windows. Right, if the command does not work on Windows then we will provide a command that should work on Windows. Right, so this is one of our main system support consideration and take a look at the pdf for further notes, right. One thing that I definitely wanted to take a look at is this executing long commands section. Right, so this course uses some long commands sometimes. Right, and we break long commands into multiple lines. And so we use this backslash character, right? This backslash character, and so you can see that here and I will note that when we are going through the guided exercises and I'll definitely encourage you to do those guided exercises with me on your local machine. So the backslash character works on UNIX machines. Right, so the backslash character works on the Linux as well as Mac OS machines. Right, if you are on the Windows machine, the backslash character does not work. You need to use the back tick character, right? In order to break long commands or you can just write a long command in one line, which is what I'm going to do in most cases. Right, so let's take a look at my terminal. Right, let's say that I have a long commander type. So for example I want to type echo, hello world. Right, and so this is a long command and on a bash right, on a unique system, I use this backslash character. So this executes just fine on a UNIX machine. Right, and this eco broken into multiple lines by using the backslash character is equivalent to one line. Right, so we can write echo, hello world on one line. And these two are the same If we are on the Windows machine we can write the same. Right, so we can still write our echo command. However, instead of r backslash character, right? We have to break the command by using the the back tick character. So now I have added my back character and I can continue on my next line. Right, and so this command is equivalent to writing the comment on one line, which means I get the same result. Right, so this is our consideration for breaking long commands. And let's take a look at our handy pdf, right. And the last thing that we are going to mention is additional accounts and services. This course uses a free kid have account and a free red hat account. The free gitHub account we are going to use for free red hat compulsory and the free red hat account we are going to use for a free open shift cluster. So that was our introduction and I hope I'll see you in the next video.
