 Hello everyone, this video is about cloud forms as a management engine for container management environment such as OpenShift or Atomic Enterprise platform. OpenShift Enterprise shifts with cloud forms as its management engine and in that context let's look at how we can use cloud forms as a container management tool. Cloud forms as a tool does a lot of things other than managing OpenShift but for this discussion in this video we are just going to focus on the container management. So all the tabs that you are seeing here are the other features that cloud form forwards but we will just focus on the containers part. What you are seeing here is an overview page under containers and it shows that there are two OpenShift environments that are being managed by this cloud forms setup and there is one Atomic Enterprise platform that is being managed as well. This cloud forms can also manage a Kubernetes cluster as well. So we are talking about three clusters being managed by or three providers being managed by this environment. It also gives a summary of how many nodes are there, how many parts, how many containers, services and things like that. Now moving on, if I click on this providers link it takes me to this providers tab and you see those three different provider environments that I have here. So let me put it in the list view. There is a Atomic Enterprise platform and the URL is here. There are two different OpenShift environments as well. Now I can add additional environments by clicking on add new containers provider and it gives me options to add additional providers if I have to. So I can give a name, I can choose what type it is, whether it is Atomic Enterprise or OpenShift and then I can provide a token that I set up in the OpenShift environment and once I give the token the cluster gets added for this cloud forms environment to manage. I can also look at all the projects across all these environments that it shows everything here but I can go drill down into each provider for example and I can see all the projects. There are 14 projects under this demo v3 provider. I have 14 projects, 16 routes, the number of services, replication controllers, parts, the number of containers, nodes, image registries, images and all that. It gives me a summary of all the things that are running here and everything here is clickable. So if I click on this project, it shows me a list of all the projects in this environment. If I go back and click on the routes, it shows me all the application routes that are available. So I can look at each route for example by getting into the details and it gives me what is the host name by using which I can access this route. Now there is also a monitoring feature here. So if I click on this guy, it shows me the time based on timelines, it pulls up all the events. This will take a couple of seconds. All the events are now pulled up and I can click on any event and see what happened during that time on the timeline. For example, this one says that it created a container with so-and-so Docker ID and this one talks about the pod scheduling event. It says that so-and-so pod, so-and-so build got started in a pod. So you can monitor all the management events. You can change the frequency, the interval, as well as how many days back you want to go to kind of stuff here. Now I can also look at the list of nodes. You can see that this cluster has four nodes and one master that is also acting as a node. I can drill down into each and every individual node, look at what the footprint of the node is, and now I can also see what routes, what services, what application controllers and pods are running on that particular node. So if I click on these pods, it shows me that there are this X number of pods running on that particular node, which is node one. So you can drill down from a bunch of clusters to a single cluster and then from single cluster to each node to see what is going on on each box. It's going back. So now back to the cluster. There is another thing that is pretty useful. This is a topology view. When I click on the topology view, it shows that there is an OpenShift cluster and all the things that are running in that cluster. So for example, looking at the labels here, which explain what these symbols mean, these things are nodes, right? It shows there are one, two, three, four, five nodes here and then there are routes, services, containers, pods and replicators, each one shown with their own symbol. Now, things of interest here. You can see when I hover over this guy, this particular pod has failed and it is shown with a red circle showing that test failed, whereas the other pods are actually running, right? And there are some that are, for example, this container is gray and it shows that the status is terminated. It's done with its job, right? So that's how you can look at the topology view and decipher some information of your interest. Now another way of using this is, let's say I disable everything by clicking on these symbols, right? And now there is an OpenShift cluster. If I just want to see all the nodes that are on this cluster, I just click on the nodes. Now I see that there are five nodes here. I can display the names and it shows the names of each of these nodes, right? And then let's say I want to see all the containers that are running on these nodes. Now the containers come up, but let me take off the names here. The containers come up, but they are not, although they are running on the nodes, they are not seen as connected to the nodes, right? Now let's enable the pods. Now you see that the containers are running in the context of a pod on a particular node. So for example, this particular pod has two containers running in it, right? When I hover over it, it is a logging pod and it has a Kibana container running and it has another Kibana proxy. Two containers, two Docker containers are running inside this pod, right? It's pretty useful. You can enable and disable whatever you want to see and what you don't want to see. The same thing for the entire set of clusters that are being managed by the CloudForms engine can be seen in the topology view on the top level, right? So if I click on the topology at the top level, now I am seeing multiple OpenShift clusters here. This is one. This is another and there should be an atomic enterprise platform circle somewhere, right? So if I disable all these guys again with ease of it, now I'll start seeing the... So there are three different environments that I'm managing. This guy has eight nodes, this guy has five nodes and this guy doesn't have any nodes, right? That's how I can use this topology view and I can see the things that I'm interested in. Now I'm back again to the cluster summary. Another thing, it shows that there is one image registry here. This is the internal registry on running on OpenShift. Let's click on that to see what's in there. Here it shows the IP address of that registry. This is the OpenShift generated service IP for the registry. Now let's see what images are there in this registry. It says that there are 10 images in this registry and there are 13 containers. So let's look at what those images are and it gives the list of images, right? And their Docker IDs as well. What I can do is, for example, select one of this image and get into additional details of what's the full name of this image, the Docker ID of this image and I also initiate something called a smart state analysis to look at all the packages that are inside this image. So for example, once I have this image selected, I can go to configuration and say, I want to perform smart state analysis. This will schedule a job. It takes some time to collect all the packages. So once the smart state analysis is done, it will have this configuration information with all the packages that are part of this image listed here. So I can click on this guy at that point of time and look at all the details of all the packages that are involved in that image. So that was a quick overview of how CloudForms management engine can be used for managing OpenShift or any other container management environment like Atomic Enterprise Platformer or a Kubernetes cluster. I hope you enjoyed this video. Thanks a lot for watching.