 So, before start, I would like to know among you, how many of you are proper DevOps engineer, pure developers, any QA, testers, support engineer, maintenance engineer, almost everyone is here. So, as you can see my talk is about best strategies to automate different scenarios using different DevOps tools. As a developer, as a DevOps engineer, as a QA, as a tester, as a maintenance engineer, we have to have perform operations regarding different scenarios in our daily life. So, we have to perform some operations like building machines, doing some operation on top of that and for that we require some lot of programming tools, some experience and basically a courage at time. But, if you are lazy, definitely don't worry because DevOps tools are always there to help you out, so be happy. Okay, since you are happy, but if you can see, this is a DevOps table, there are lot of tools available like database, CI, implement, cloud, monitoring tool, logging, release management, collaboration, security, testing, build, repo management, SCM. So, if you see this, then definitely you would become confused. So, today we are going to talk about what are the best strategies which we should follow so that we can automate our different daily tasks. Daily tasks for DevOps QS is admin support team. There are lot of different tools available but in this talk, as per the scenario, we will discuss what are the best tool available or should be the best strategy. We have some statistic reading. In the IT industry, which companies are using which tool, frequently for which scenario. So, we will discuss about that as well. So, starting from requirement gathering, starting from issue tracking till reporting of release of the product. We should use DevOps tools so that our life will be very easy. So, that's the main motto of this talk. As a project management tool, people might aware about JIRA and open projects. So, those are the two tools which are using frequently in nowadays IT industry. So, you can see basic difference that using JIRA, JIRA users can create new issues in pop-up window. And in open project, you can create new issues from the both package list. So, here are the basic difference between JIRA and open project. In this talk, we have lot of things to cover. So, I am not going to explain in detail. But this is basic, screenshot of creating issue using JIRA. And this is basic screenshot of creating package and creating any issue tracking using work project. So, in work project because there is a GAN chart where you can actually see the timeline period etc. To track your project or any issue. We talk about the comparison between JIRA and work project. Data security and time tracking is one of the major issues here. Because in both JIRA and open project, there are equal amount of add-ons available. But the thing is, if you go with the JIRA, you need to buy some of the add-ons. But with the open project, you will have it by default. So, that's the main advantage of open project over JIRA. So, many times we need to install OS, but it's apart from provisioning the machine. So, on the machine, we sometimes need to install the OS using GUI tools. We need to previously people used to click on next, next, next, setting up time and etc. To install any OS using GUI. But there are some tools available using which you can install or install OS and basically automate the scenario during installation of OS using those tools. So, open GUI is a tool which is operating system testing tool. One of the major mode of this is operating system testing. But the thing is, it takes an operating system, ISO or disk image and using it domain specific language. It conducts a series of tests consisting of keyboard and mouse input while analyzing the screen output for specific matches. So, it called it as a needle to ensure the operating system is behaving authentically. So, basically in very basic terms, they compare the screen shots which we will provide to that tool. And as per that screen shot, they will automate the things. Like open GUI is also one of the tool which is currently using frequently, which actually automates anything you see on the screen using the image recognition method to identify GUI elements. So, it allows us user to automate GUI interaction by using this screen shot. As I mentioned in open GUI as well and in security as well, we can compare the screen shots and we can automate it. So, open GUI actually helps you to install or to automate GUI things. But if you are using a format to provision the machine for physical service or virtual machine, then definitely it will make your life very easy as you could heard the talk about format metalized service. So, definitely format is very good tool available in the market and which is currently using frequently for provisioning the machine. But the thing is if you are using a format, you definitely cannot deal with the hypervisors. So, overt is a tool which is currently using to manage the hypervisor level, virtualization level of automation. And even format have overt plug-in as we discussed in yesterday's talk about provisioning the machine or provisioning the service on pop-up cloud or on pop-up open stack we will come on that part later. So, you guys are mostly aware about configuration and management tools. So, there are lot of discussions where going on in last 2-3 years which is the best configuration and management tool available in the market. There was a competition regarding puppet shape and ansible. You might aware that both puppet and shape have agent master architecture where ansible is agentless. Architecture. So, you would see the difference that for puppet and shape we have agent master architecture and their terminologies, their scripting is pretty much harder than ansible. But ansible in let's say since last 2 years is using very frequently and most of the companies currently using ansible for any configuration and management automation. Ansible as you might know they have providing lot of modules available for the containers as well or open stack as well. The modules need to just pull down and we can do our stuff using ansible. So, that's the main advantage of ansible over the puppet and shape. Still some of the companies or some of the organizations are using puppet and shape as per their requirement. But you can see that that is the statistic of comparison between ansible shape and puppet. So, you can see the favorites around 197 which is around more than double than the shape and puppet. So, even you could see in upstream level if you talk about open stack previously they were using puppet but now they are using ansible. You can see the fans, boards and jobs which is far more than around twice than the shape and puppet. Ansible tower how many of you heard about ansible tower? Almost half. So, I will talk quickly about this. So, ansible you know it is a configuration and management tool. We can write playbooks. It is agent list and we can directly deploy directly manage whatever we want to manage on the different servers. But if you are not interested in doing CLI part ansible provides you ansible tower which is basically you have at work on top of ansible. Where you can see your ansible playbooks ansible jobs are running you can schedule it you can write the playbooks over here. And it makes your life easy for usage of ansible. So, that is the main motive of ansible tower. So, currently lot of companies are using ansible tower as well because red and also have lot of support available for ansible tower. So, yeah you can try it out because it is very frequently you using tool in the market. So, infrared you already aware about that how many of you aware about infrared you moving. So, it is basically like it is basically feature by provided by ansible like CLI and brings us some stuff over using infrared you can directly deploy your jobs using ansible. So, if you are using any cloud I will be mostly talking about open stack because I am a red actor and I support open source. So, how many of you aware about triple open stack or open stack only one. So, basically open stack is a private cloud. So, previously before two three years back there are three basic nodes are requiring open stack if you want to deploy open stack. So, there were like three nodes like network node compute node and your database node. So, those three nodes should be there for complete open stack and previously we had to deploy those three nodes separately. But since last two years maybe triple open came into picture where open stack or open stack they have deployed. Let us say you have only one machine with lot of required hardware resources. Whatever the code which you had to manage separately previously using triple O you can manage install deploy in single machine. So, that is the main advantage of triple O many companies are using triple O instead of open stack. They you just need to do some stuff and install under cloud and on top of that they deploy over cloud. So, that is the main difference between previously used open stack and triple O. How many of you aware about RDO? So, you might have found in our exhibition area if you have not been there please go there. So, RDO is RPM based distribution of open stack. It is basically a community which supports to deploy open stack on CentOS Fedora RL basically a RPM based Linux. And they have both support as well both community as well. So, if you want to deploy open stack on top of RL CentOS or Fedora any RPM based Linux please go with RDO. So, that is the current happening thing in the market that people are using RDO instead of open stack. Hit template anyone of you aware about hit templates. So, hit template is basically orchestration tool provided by open stack using which you can orchestrate the server deployment or anything you want to deploy or configure on top of that server or anything you want to play with the open stack hit templates are the best options. They also have user data section over there where you can directly write your own scripts like shell scripts and all. And where the server will get deploy on top of open stack hit template will run that user data section. And let's say on top of server that server we need to setup like a paid we need to setup like any database or any tool then it will get deploy as soon as the server will get deploy. So, that is the main advantage of hit templates. Many open stack users a best is also plug in provided by open stack. So, it's a basically a SD plug in provided by open stack where they have written the test API based test for each and every plug ins of open stack. Whatever let's say you have deployed open stack and some particular plug in or component is working fine or not communication is going well or not networking is working fine or not. They best have a test available API based you just need to run the test test. There is the scenario. Now we come towards the containerization part where you could see since last one or one year or two years many companies are containerizing their services their applications. So, aware about Kubernetes swarm and compose you heard about Kubernetes in previous talk. So, basically these are the orchestration tools using which you can manage the containers orchestrate the containers. So, I found some of the interesting different different points between those three orchestration tool for containers. But if you see since last one year or two year community wise and overall support wise Kubernetes is very much larger than swarm and compose. The swarm and compose is about to die because Kubernetes is providing lot of lot of features for managing orchestrating the containers. Okay. So, have you guys aware about open chip? So, it's basically we can say a wrapper on top of Kubernetes which makes developers like easy to manage the containers through. Even IDO provides some mechanism to deploy open chip on top of OpenStack. So, if you just deploy OpenStack sorry OpenChip you cannot play with the infra. But if you deploy OpenChip on top of OpenStack then definitely you can play with infra and Kubernetes. So, first step I'm sorry OpenChip origin is a upstream product and enterprise level OpenChip is a downstream enterprise level product. And Red Hat is also providing support for OpenChip. So, OpenChip is basically a wrapper on top of Kubernetes. So, handling Kubernetes commands is sometimes maybe very hard. So, using OpenChip we can do it easy. Even top of OpenChip we have OpenChip I.O. You might have aware about OpenChip I.O. Anyone? OpenChip I.O. So, OpenChip I.O. is basically like IDE for OpenChip which basically makes your life easy to handle or manage the OpenChip. So, you can read about OpenChip I.O. OpenChip online OpenChip dedicated OpenChip. So, we have this then we need to go further. So, basically here I'm trying to show the example if you deploy a particular container. And you want to see the particular container is working fine or not as per the expectations. Then you can write your scripts testing scripts here in the document itself. So, that if you deploy a machine or if you deploy a container, then at the time of building container, the test will execute and script will execute and you will get to know that whether your test cases are passed or not. DeGauss, anyone aware about DeGauss or DeGauss tool? Okay. So, DeGauss is a tool basically it provides you a functionality to test your application in CLI level. They provides us a interface, command line interface using which we can write some rules in YAML or JSON format. What it exactly does is whatever we write in YAML or JSON, they check whether the particular rules are working fine or not rules are limited to mostly users, groups, packages, services, etc. I will show you example so that you will get to know more clearly. DeGauss is basically a wrapper on top of CoS for the containers, to test the containers. So, let's say DeGauss in it, Golang is the name of the container and they have provided a, they will provide us some interface to write the YAML or JSON format. So, here you can see I write, I wrote a rule app running through and after that I have written some of the rules for both TCP ID, ID is running, listening or not, process is running through or not, HTTP. So, and then you could see the, they did do DeGauss run. You could see container is running, running test, process app is running, port is listening. So, that kind of testing can be done using DeGauss. So, it's a very good tool available in the market and many industries are using that tool to test the containers. Monitoring tools, we already know how many people are using 90 voice and Jmeter as well. Monitoring our QS is also a good tool. New Relic is also good too, but they go for New Relic because it's not an open source. A building tool you can see there are top-rated automation tools include Radar, Timstreet, privacy and Jenkins. There are other building automation tools, Circle, CI, Poundoo and Apase Mabel. Databases, okay, so you might have heard about Radies. So, Radies is basically a database, many top-level applications are using it like Twitter, Instagram, GitHub, Stack, Overflow. So, it's basically, it don't have a database which it like highest will have and it's a main memory database. So, it is very fast as compared to MySQL. And for voice-based database, many companies are using GoogleDB and Cassandra. Cassandra is mostly using for cluster-based architecture and where we actually don't want any single point failure. So, whenever there are some servers of databases and one of the server, let's say, will go down, then definitely, sir, Cassandra will provide us a different server with the backup. So, that's the main advantage of Cassandra. Ulstack, you already might have heard about it. Many people are using Ulstack for different, different reasons. It mainly deals with the searching, with the database, then logging and then your visualization comes. So, many people are also using this Ulstack for reporting, as a reporting tool as well, because it will provide some great graphical such as like biodagram, graphs, etc. So, if you talk about DevOps, then definitely, you can't proceed further if you don't talk about Ulstack. And CICP, we already know about it. Many companies are using private CI chains, etc. And as a report, people are using BERT, JASMAL, report as a tool, which is like, this name is Allure Report, which is mainly used for showing where some tests are running, are passing or not. So, if you want to test something or if you want to do unit testing, day testing, then definitely, it would be the good tool because they will provide you good graphical structure like, let's say, you would see, there are biodagram and overall graph. And the main thing is, it can be easily integrated in general. So, that's the thing I wanted to show with you. Any questions, if you have? So, for configuration panel or sort, because I didn't see in the comparison this. Yeah, so basically, it is a good tool, but the thing is, community buys and support buys, as well as good support. And the company which are using Unux, they could go with the expert because they will have a lot of good support.