 Thanks for the introduction. So now everybody is talking about Ansible, Ansible, and Cloud, right? These are buzzwords nowadays. Then how can we coverage all things under one roof, right? So many of the organizations have multiple crowds, or maybe on-premises, like infrastructure, let's suppose your example, Microsoft Azure, SCVMM, then your VMware, the biggest player in the market, then Cloud, right? There are various cloud providers as well in the market, right, like AWS, Azure. So how can you manage all the things under one roof, right? So you want some unified solution to orchestrate all the things under one roof. And like my colleague, community manager, Carol can mention about the orchestra, right? One conductor is there, so he actually manages all the things, right? Same thing ManagerQ does in the same way, right? So there are some points about ManagerQ. I didn't wrote it out. I just copied from the ManagerQ.org. Eventually you can check it out, OK? So the first thing is your continuous discovery. So when you deploy it, ManagerQ is in first appliance. You can install that particular package in your virtual machine. You can run it as a bare metal. You can run it as a cloud or as an instance or as a VM. So continuous discovery means whenever you add your providers, any of the providers, like Azure, VMware. So what you can get, you can do multiple things, right? Customers of customers can create or users can create multiple VMs, instances, anything, right? So that could be captured by your appliance. So continuous discovery, emphasize that thing. Again, there is a compliance, right? Compliance nowadays, security plays a vital role in the market. So everybody is threatened about the securities in the cloud area. So there are some SCAPs are there, right? SCAP. So there are open SCAPs as well. Contains some set of rules that your system should be like that or not. So ManagerQ does that thing as well. You just need to create a profile policy under that and do the compliance check on your instances of your providers, OK? Next. So optimization and self-service, OK? So basically, what actually it does? Optimization basically meters your thing, right? At the end, everybody is looking for the cost, right? Whenever I'm sharing my resources to the end user, I'm looking for the cost at the end, right? That thing is free until and until it is open source, OK? So it will actually give you the insights of usage, unlike some proprietary cloud services or on-premises services as the metering related to your memories, memory utilization, network utilization, space utilization. Similarly, you can capture that thing. And based on that, you can create your own charge back reports. Means you can charge according to yourself. It will generate reports for the same. Then self-service. For the self-service, I'll give one analogy, right? Everybody uses the shopping applications, right? Whatever you want, just I want some hard disks. I want some pendrive or anything I want. What I did, I just search it, just click it, finish it, right, and order it. Same thing. Create a bundle of your virtual machine, which contains your business logic. Suppose you want to deploy one application. Create one VM, add your business logic in that, configure a database, and create a bundle of that. Order it via catalog. This is self-service UI. What at the end user need to do is click, select your VM, service catalog, order it. And at the end, you will get one IP address which will use for the hosting your website. There are four features, key features, of ManagerQ. One is agentless. So you thought, like, I'm using two providers, right? One is AWS, another VM, where both are. One is Cloud, one is Infra. So you think that I have to run any of the package service or any plugin? No, you don't require it. You don't need to rely on this. So what you have to do, you just have to. There are some SDKs that are available, so you can use that. And behind that, ManagerQ uses the gem package for that, and it will discover the things. Then smart set analysis. It is one of the core features. Like, by not touching your VMs or instances, it will get all the data which is required to you, which contains your user data, group data, packages, files, security-related things as well. It does work for Windows as well. We are more concerned for the registry entries, right? It will scan those as well. So if you want to retrieve any particular version of any of the package, you can do that with the smart set analysis. Again, virtual appliance. As I said in the beginning, you can use ManagerQ in the appliance as well, right? So scalable architecture. Basically, you can scale your appliance, which have multiple database applications you can do. So now, Ansible. So in the market, the automation is all of the, means all area, automation is captured by Ansible. So you can think of that to automate by sitting at home at any location. To do automation on the inside, you can do that thing. So here are some key features. Automate, accelerate, collaborate, and integrate. So Ansible. You can automate. You can do things like installing off packages, configuring your data center at various locations at the same point. Ansible basically uses the connection, SSH keys, so you don't need to worry about your credentials and security thing. Once a key is shared with the targeted host, then you can do a number of automation with that. OK. The next thing is, so basically, we concern about the use cases of Ansible, like it does provisioning, then your configuration management, app deployment, continuous delivery, security, and compliance, and orchestration, right? Anything having shared with SSH key, you can do everything with the Ansible, OK? But so the key point of my presentation will focus on how you can manage all the things, all the entities with ManageIQ, right? So you are managing your infra and cloud stuff with the ManageIQ, like your entire cloud and your infrastructure on premises. And you want to use, to manage those things, you need to use your Ansible, right? So what you can do, we have added support in the ManageIQ for the Ansible. So what it does, it will actually add the headless tower inside the ManageIQ plans. And you probably will do the automation with that. You just need to have a playbook with you, the host credentials, the targeted host credentials, like SSH key shared. And then it will give you the desired result. So right now I'm using Red Hat CloudForms Managing Engine, which is a downstream version for ManageIQ and Red Hat product as well. So for Ansible role, what we have to do, we have to just navigate to users, configuration. And then you have to just slide down there. OK, so here you can see the server rules are there. So the server rules are basically the processes which are running in the ManageIQ appliance and which will give you the basic installation functionality. You don't need to install embedded Ansible by your own. So just need to slide down and then save it over here. I already saved it. It requires 10 to 15 minutes time to get enabled. It will fetch the Ansible packages and install it in your system. So after that, you have to navigate to automation, then Ansible, and then the projectors. First thing you will after starting the server rule, you will get a notification over here like this. So your embedded Ansible server has been started. Another role has been activated. So after seeing this message, this problem will enable for you. So click on this repository, add a new repository. Then you will find you can add repositories where you placed your Ansible playbook as I discussed earlier. So you placed wherever you want on your version control system like Git, then your GitLab and all. So you can place it there. So see I just add a name, then select the credentials, and give the URL. If you are using a private repository, just before that you need to add credentials for that and select those credentials from here. So for sake of timing, I have already added one repository over here. So here is my repository, Ansible repository, which has 26 playbooks. So by clicking over here, you can navigate to another navigation for Ansible here. There's Ansible and then playbooks. Same thing, same output you will see over here. So right now I'm more concerned with the list. This is, for instance, yaml file. It contains the just getting a fact from that particular EC2 region. So in order to run the Ansible here, you have to use the catalogs. So I'll guide you through the catalogs, how we need to create. So catalog is basically a bundle where you can add your playbook to order the service. So here I have created one service over here. I did these things. Hello. So you have to give the name, then description, then display catalogs and all. So you have to select your repository that you added here. Then the playbook, which is suitable for your operations. Like if you have multiple playbooks, you can select, you can create each catalog for each service or each playbook there. So I am running on this machine only. So I'm using the credentials default. So I don't require to exchange my SSH key or add any credentials of that machine. So next I am running it on my Amazon cloud for this example. So I'm selecting the cloud type is Amazon. Then cloud credentials will be Amazon credentials. I'll show you how to add credentials. Then you can set the logging output level. If you want the verbosity as well, like we have in our Ansible. You need to add one dialog as well to represent the inputs and all. I'll create one catalog in front of you so that you don't miss the thing. So here you have to select the Ansible playbook. That's it. And for credentials, just navigate to here. Ansible and the credentials. So under which you can find not many things. Just add new credentials. And you can see there's many types of providers or maybe the credentials through which we run our playbook. Through which on our targeted node we can use it. So right now I have added Amazon. Then you can add Azure, Google Component Gene, OpenStack, Red Hat Virtual Edition, VMware, et cetera, et cetera. For our demonstration purpose, I have added Amazon Credential over here. Now we need to order the service. Before ordering, you will create a catalog item. Then you need to create a catalog for the same. So here I can order this service for just a time consuming process. I have already ordered some services so you can see the output of it. Here. So unlike you run your Ansible playbook locally and try to manage your system remote or whatever the managed system, then you can see the same output. So you can see this. I just ran my playbook. I can show you the playbook, what it contains actually. So we can see the output over here. So I have my one instance into the APEC region. So you can see that is captured over here. This is just a listing of facts from the specified EC2 instance, but you can also include your playbook. You can run a concurrent playbook as well in that. Let's create multiple services and order it on a go. Then ongoing service request you can see under services and requests over here. So you can see I have played with the request over here and I retired one service as well. So you can remove that service after the work has been done. So this we can do with the normal machine, right? But what is the use of this managed IQ? So here is we have policies. So I have added one EC2 provider over here and I can show you directly instance so that you can understand the EC2 and thing. So here I have only one instance available over here. So here are the policies. Policies are nothing but a set of instructions. After triggering one instance events, certain actions need to be performed. So for that you can also run the similar thing. So I can guide you through that, creating a policy, then action, then policy profile and assign it to it. So before that I have already created one action for that which is list instances. So for that you need to navigate to control explorer and select the action accordion. And then I can just create the new action. So list instances I give the description. Type of action is run my Ansible Playbook. But similarly you can do multiple things with that. Then which is my catalog. So before creating an action, I need to create a catalog first. So it will be automatically triggered out. So I can give it, so where I need to run this catalog or means the my ML playbook. So either I can run it on local host or a target machine or a specific host. So you can give the comma separated IP addresses over there to run this particular action concurrently on those machines. I have here selected a targeted machine. So I just need to save it and click and cancel. So whenever I applied this policy, when I apply this policy profile on certain instance or VM and when I trigger certain action, that trigger certain event which eventually invoke this action. I'll show you how it goes. So here I have created one policy because I need to control the things. So I have created a VM control policies. So I can show you here. So how can we create just click on this configuration, add new VM policy, then I give a description, the name of your policy, add it. So I have added here list of instance policy then you need to edit event for that. So I have already have one event called attack complete, but you can assign more events to that particular thing, not to particular instances. So here VM operations are there. So after creating any of the instances provisioning, so VM provision complete means when you create a VM at that moment, that event is generated VM creation. So at that time if you want to run any kind of playbook, you can run it. So just need to select this slider, no to yes and save it. So for a sake of simplicity, I have added over here attack complete. So I just need to add attack to that particular instance or VM and then which action need to be triggered, action which I created. So here you can see whether this, if we got an event, so events may be two types or true or false, event may generate or not. If event is generated means condition is true, then select this action. Else you can also select any other actions need to perform. So you can send out a mail that your action didn't perform well or even didn't trigger so that we couldn't perform any action so that. So I have created over here. So now next task is that create a policy profile. Here go to the configuration, add new policy, choose the policy which you want to add, give a beautiful name over here and save it. So I have already created that. So this is my policy profile to list instances which is having this, this which is having the attack complete event and the action need to perform which we created. So now we get to compute cloud instances and select your instance there and manage policies and select this policy. I have already assigned this policy to my VM. What you need to do just make a tag completion. So again, select the VM or instance, edit a tags, company tag, department, suppose engineering. So now we save it. After saving the tag complete event will be generated and by navigating to the task folder, you can see the action is performed. Action is executed that is run. It is under request, service request. So request will be generated unlike it is invoking the playbook. So right now that machine, that instance is in a power off state but still that event is triggered. So we'll see what result I can get because I'm not sure service is active. I guess it will run because we've only added the list instances. We are not performing any of the operations on that instance. Let's see how it goes. So it's just a matter of your playbooks. So you can, just now I showed a demonstration regarding the EC2 provider. You can have your multiple providers like VMware, Azure, then your SAP MM, Google Compute Engine, VMware and OpenStack, Red Hat Watch Flageation and every provider you can add it over here, create a policies, create control policies. Before that, create a catalog, then add that catalog into the action, whichever playbook you added into the catalog will be run on that particular machine after triggering that certain event. So this may think I have only example playbook with me but you can apply, you can do your own playbook as well. You can run your playbook as well. I guess it won't run, task has been finished, wow. Nice, I didn't expect this. So you can see here we've got the third active service instance and we can see, we can get the similar output that we have because we're just getting the facts from the EC2 instances, that's it. I can see if I have my playbook, I can show you. So I have repository here and we use this playbook. Localhost and task is just gather the facts, register the facts and show the debug output with the facts that we have. So similarly you can see over here. That's it, I have on my demonstration but you can use it of your playbooks on all things on your machine and this is how you can orchestrate your cloud, infra providers with Ansible using Manage IQ. And thank you for listening at PatientQ. Thanks a lot.