 Now, DevOps and open source DevOps, now this is something which is my forte and what I have seen since morning is most of the sessions are now WordPress and the stream right. So, before I proceed I would like to know from you people what is your expectation from this session, why I keep here basically. Anyone what are you looking for from this session and you take away is what you want to learn about DevOps or Cloud open source. Anyone cool that I'll share my agenda and you see if it aligns with what we're looking for. What we discuss is brief about the so called DevOps. It's a buzzword in the stream right. So, what is this all about? What is the benefit of using DevOps or if organizations adopt DevOps? How are they going to benefit? There are different stages for DevOps. So, we are going to just go through them. And for me the key thing is the people who are working into open source, they are not a DevOps and WordPress teams which are open source available free teams. I would like to share from a DevOps pipeline what are some of the common use softwares which are available open source where you don't have to pay. So, this is what I'm going to cover in my couple of slides. Your team, you know, I think it was a team right, right? People are back from the snack shopping. So, let's start about DevOps. But before I proceed, this is something which is like recent shift in the software paradigm, right? DevOps is one. So, buzzword has been there around 4 to 5 years. Before that we have a typical sequencing model where you used to follow the agile model, big release cycles, complex scores. One more I think software. Now we have a question which says automation ability. So, how does the pre-demox startup? So, basically he used to have a software team or a developer. So, this is a typical software developer. He used to do a lot of coding. He's a nerd guy. Nothing else in his life. It's all about code and work. And he used to code. Once the code is done and you have your bundle software app ready, that's the code for the deployment. The management says, yes, we are good to go. Yes? This was one side of it when we talked about DevOps. We saw the developer. There's another type to go back to DevOps, which we typically used to call as system admins. So, what was the feeling of system admins and his team? When the developer is doing the job, I think something similar to this. Because they're not sure what the developer is doing, but he's doing the deployments into their production. If something breaks, it's going to be a headache for the system admins. Now, they are called DevOps. They are the system admins. They don't know anything about the core part. No offense. I need a system admin here, but then here. They didn't know about the core part, what went wrong. But it's their bucket to fix it. How to do it? Now, the manager tells you, if everything is not ready, we have tested a QA, a UAV, everything is already done. Let's do a deployment, right? What possibility to go now? Does the deployment go wrong? We haven't tested all scenarios for our cases. Everything is all covered. Nothing could go wrong. We don't want deployment. This is a scenario that I have seen in my career. Most of the times, deployments used to go wrong. Due to some of the other reasons, it's not always because of the code. Could be buggy code infrastructure, third party softwares. Nowadays, we use workloads like Docker. So, third party Docker images. One limit is over there. So, it could be anything. And they're not sure. But the deployment goes for a toss. There are scours to your rescue nowadays. I have to keep a tap of time also. Yes, you just have 25 minutes to cover all these things. So, when the deployment fails, there's another 18-5 between there and the toss. It's the blame game that normally goes, right? It was low-fold, it was low-fold, and yeah, it continues. No one is ready to accept their mistake out of all. So, the typical scenario most of the developers are the people who are from a developing background. They will associate with this. So, it should run on my machine. It didn't work in a function environment. I'm not too sure about that problem. Right? It's a common use, yes. I think Docker solves that problem to a certain extent. That difference on your machine and any machine that supports Docker. It should run on that machine also. But it's a typical scenario. Everything is on fire and you're like, okay, what can I do? It was not my mistake. So, now, Docker comes to rescue as a superhero. You know, deep dive basically to what all DevOps is all about. But just try to cover the essence of it. What is typically a DevOps lifecycle? What are typical tools which are required? And what are the open source options which are available? So, with DevOps, there are different definitions. Different people say it differently. Some say it's all about pool. Some people say it's all about culture. Some people say it's all about developers getting smarter without automation. Other people say a system should be more smarter to understand code. So, if you see from a larger perspective, each one has their own definition. So, it's something like this. It's a feature. It's a culture. It's an infrastructure of a code. It's collaboration between teams. It's all about automation. So, yes, from my viewpoint, I think DevOps is all about this. It's not one single thing. It's not only culture. It's not only collaboration. It's not only automation. It's not CI CD. It's not Puppet, Ansible, Chef, Terraform, Theranus. This is the end point implementation. And that's where we talk about DevOps life cycle. There are different life stages associated with the life cycle that you should go. And then for each stage on life cycle, you will see what are the alternate open source options available for you. So, benefits of DevOps, if you see at a high level, you have a few of failures, better experiences, faster updates, faster deployments, faster deployments. If you are able to catch up errors at a high level or initial levels, that is the left shift principle that we follow. So, definitely more relevant production, right? Short life cycle, lower risk, efficiency, those are some of the benefits which are covered later on. So, this is a CI site data that I got. I think this is a bit one year old, 2018 data. So, the benefits for organizations that have implemented DevOps is kind of underlined. So, increased performance of software will allow you 53 percent. So, more than 53 percent or 50 percent, organizations feel their efficiency of software has increased or improved, correct? Increased collaboration, 48 percent, new software services, 35 percent. A reduction in spending cost setting. So, 46 percent, that's a good number over there. So, why do you feel a reduction in spending? Any answers? How do you save on money? Anyone from management? Who is all about money, savings and those things? They should have an answer, right? Yeah. Yeah, CIC, who are you talking about? That's true. So, I think you are talking more from a city first time thing, but you think about each life cycle. So, we wanted to be vlogging. If you have proper coordination in place and tools in place, definitely there is a manual reduction, right? So, reduce on manpower and reduce on failures. Your main time to failure reduces and you are able to catch it up early. So, your delivery time increases cost increases basically. So, we saw some of the benefits of DevOps, right? So, this slide is basically just a vision of those things. What are the benefits of adopting DevOps? Be it from cost perspective or automation perspective, those are the ones. Building time of silos. And this is one of the important things. What was happening before the DevOps era? There was a dev team, there was a QA team and there was a separate system admin team which had completely unaware of the entire software end to end. There was a cycle. Cycle means you have your own empty space and DevOps has to break that cycle. So, a group of DevOps engineers are basically interacting with your developers as well as your QA engineers as well as your development teams and your production engineers or your system admins. So, that cycle was always the issue. No one knows about what they are doing. With the active of DevOps, this being a standard model and this was necessary. And this is where we talk about DevOps as a culture, breaking the silos. Faster development cycle, obviously with tools like CNC, implementation, lift kits and those kind of things. Earlier development cycles if you go through the data, the problem used to happen once a month or twice a month. That was a kind of ratio that we had. I thought it would be back to Monday. And that means we used to let prepare so we used to be a big festival. Everyone is at the system and it's like development is happening, we have to do it. Now, with coming of CD, what Sir mentioned, right, continuous delivery. Every hour and then, every hour, companies like Twitter, Apple, Facebook, those are doing continuous development and daily needs. Different features, different teams, but back and front things are changing per minute. So, thousands of developers per minute is happening, but we don't see it. So, that has been with the use of technologies like DevOps or automation. Increased collaboration with three teams. So, yes, as the silos broke down, there was a better collaboration on different teams and team members, which basically led to more productivity in terms of organization output. So, organization as a whole is performing better because each team is integrated and talking to each other to know what is happening across the teams. Reduced time to market, so it makes sense your product which used to take, like if there's a development that is happening in a month, different teams have to do different deployments, so it will take a lot of months to build the product to market. If you have different deployments at a rate of 10 deployments a day, within a week, you are ready to go with your product. So, that explains a reduced time to market. So, product from MVP phase two final customer service is all about time, cycle is reduced. Stable production environments, so with the effect of tools like the monitoring tools and logging tools that we will look into, you are able to catch up issues, production issues much faster, there is an alerting mechanism which alerts you as soon as there is a break in the production environment. There is a page at the KLM, there is a Slack alert, teams who are responsible, then they can start the action and they fix it immediately. Instead of like someone in U.S. who will wake up at his hour at different times of the time, and then we will look into the issue, it will fix it up or we found the Indian team and then Indian team will do next day. So, that is the main stable production environments where you are easily able to identify bugs and fix them at a much faster pace. Since you are able to identify bugs and issues at a higher at a faster level and fix them perfectly, your quality of software is also improved. The final product that you get is much more improved than the initial one. And better realisation of resources, this is both with respect to your hardware and manpower. Some people who are working there, they are not properly utilised effectively and also in hardware. They are not misusing all this considering hardware. They are also at a high level and as I said, we will talk about different stages of the house or life cycle of the house. So, before I share, the slide talks about it, but I would like to know from you people what are the stages you know or what are the stages you follow when you are talking about certain stages. Come on. We do a lot of development work in organisation. We have the only general process. So, what process do you follow? And it is there on the slides. So, even if you can read, you are smart, you can read and tell them. I see this kind of response many a times. People don't feel shy of raising hands and talking. It shouldn't be like one cycle session where I am doing all the talking and we are just taking it. So, university lessons and all right. And then I am just ready to finish off the lesson. I just want to give you something that you want. We have time for Q and A at the end, but in case you have some doubts, I would love to take them now also. But yeah, let's proceed. So, if you talk about high level with the house life cycle. So, what happens is you have a developer who does the development. So, that's a development life cycle and you have certain tools like it and source code management right. That means the next level where you have just things, which is the CI CD pipeline. And depending upon how tightly coupled is the just things cycle, you can do a lot of stuff with Jenkins and similar tools. Automatic testing, education testing. If you are using something like Docker, security, Scania, you can have, so happy with the checkpoint quality and a lot of other things. If everything passes through Jenkins, you get a final build. And this bit says that it is ready to be deployed, because we have a lot of code and testing and everything in Jenkins pipeline. So, that's the second CI CD pipeline is the second one. You do development through automation tools if you have already achieved automation, something like Ansible Terraform. That's the third level where you deploy. Right. After deployment, you need to monitor whether things went fine or there's a red flag. So, directly there's a monitoring solution. That's another life cycle. You can also do logging and alerting. So, alert systems which tell you that there is an issue with the system. And finally, there is an SRI which takes a corresponding action how to resolve that issue. So, those are certain at a high level, certain life cycles which you will see. So, as I said, starts with continuous development, continuous integration, followed by testing, and then you deploy. So, that's continuous deployment. So, CI and CD there, continuous monitoring, continuous logging, feedback, is it a little thing where you take feedback from the system or your users, and take a corresponding action on it, and taking these operations. So, that's an operation key which basically resolves your production issues of both kind of us which takes a handle on it. So, we're coming to a lot of things. I've been talking a lot about DevOps, not mentioning a single word about WordPress and those things which is a theme for today. And I see a couple of people here with different face, facial expressions. So, someone who is feeling like this for people who are sitting at the back this guy says, I have no idea what's going on here. And I just want them to affect us because we're halfway to the presentation if I ask, if you were to be like too shamed. So, anyone that has similar feeling, see I like audiences like this, it means two things. If I get too smart, I'm too smart, I couldn't make it again. So, it's either like all wrong or all wrong case. But I hope no one is like this. So, what happened once is I had just had this in the presentation. I was talking, I had a much larger audience at the front of the fan. And when I asked about this kind of feeling that someone feeling like this, I don't know what people understood out of it. I talked about fans going up and I was like, no, it was like 45 minutes after 25 minutes, people are telling me that they can relate to this. And I was like, really? And then I checked with a couple of them who have raised their hands. Do you really feel like this? No, no, we thought that we were asking who did it feel. I just rephrased my question and then again checked with them. Do you feel that whatever I'm asking I've been sharing throughout right now makes sense. This side I think audience is pretty smart. It's not only WordPress developers but then yeah, much more mature than WordPress people. So yeah, we go to the life cycle of devops. Different things. I think that kind of skipped because of the time. So now what we're going to talk about is open source basically. I had conduct for the CICD in those things but that takes much more time. At least 10 more minutes and we're done. So I think that kind of skipped and now we are moving to open source. So since this was about devops and open source management a lot of you when I practiced over lunch and pre and coffee breaks people told me we are from small startups and when you're coming from a small startup working with a small startup you won't have bigger profits, right? Money is the big question. So if you enterprise little softwares so company, bigger companies like Anansi and all they can afford to pay and they have associations and partnerships. What about a little startup? We look for free and cheap models so this is a paid version what is ordered into free open source available in the market. If you find something you will implement it. So let's talk about that. Why choose an open source thing? So basically when it comes to open source tools this is something that I would like to come from two people this is not related to devops devops I understand might not be a forte but then yeah, open source is common thing all open source developers use free themes so what are some of the benefits? I am sorry? Cost is definitely yes no licenses required also what else? Yes I understand but then how do you see that community work? What is the connection for you? Basically you can create the benefits of the open source tools. So I think that as a bigger community means a bigger support when you have enterprise level solutions you pay for the support but when you have an open source community you have a bigger team to support you without any cost so we will cover those points I think those are the things which are already there on the site so I will just revise that for you What are the points for open source? Come on guys I am not sure if she is trying to take a pic of mine or if she is trying to get a boyfriend and there is a camera on was it my pic that we are trying to take on this slide or was it like that? Ok ok But a quality code yes that is another point yes But a quality because security because it is coming from a community which has a lot more smart people smart developers and all the growth so definitely you can talk about security also sometimes we talk about open source and vulnerable softwares but this time you will take a positive side of it you can assume the software is used by millions of people mostly so no software cost that is what I can say it is all free so definitely no cost involved over there some of the times it is an open source version if it works or we use it there is no motivation there is no licensing fee and all those things when there is nothing and that is an important point no when there is nothing as in when you have to write the software you are dependent on that particular vendor to support your partner services at that point in case in future there is a time or need when you want to move out your entire code is coupled along that part of it and it becomes difficult to move out of that particular vendor so that when there is nothing there is no license version of long open source softwares but in open source that is not the case you have multiple other options they do not have to be so it is all free you design your architecture in such a way that in case if needed you can always move out of top of it so I think this was again covered greater community support which is free so you have big community which is there and they give you support which is all free greater flexibility for customization since it is open source you can do all sorts of things on top of it add your own wrapper, add your own customization no one stops you which is not the case with the proprietary software it comes with certain ifs and buts this is the amount that you pay and this is what you get you do not have a customization option on top of it you might get customized softwares but then you have to extra pay for that you cannot do it on your own because they will not share the code to you they do it at their head for you as a customer customization experience this is not the case with open source it is all free you can add your own customization on top of it simple license management that is pretty simple and clear there is no license to manage for different users it is all free so that habit is all gone you do not have to think about when to remove the licenses how much to pay in this year 200 users next year do we need that we do not need that those are hazards are all gone and easy to audit it is an open source community there is a software to have a lot of limitations over it so those are some of the top open source tools that have benefits and not only for when I am coming from a DevOps but not only for DevOps or any particular domain this applies to all what are the objective benefits of open source tool why should we use it, why should we promote it and now when we talk about lifecycle of DevOps we talk about CICV and different stages for each stage you will see that open source tool is available so DevOps and open source tools we started with development and I talked about Git and other options so let us see something we called as SCM source code management so this Git SCM was a real serious money move I mean these are the ones which I found interesting they were on top of my mind so this is not an exhaustive list there are many more which are available and you can find something superior to your taste so this is the source code management next is the CICV before CICV I think there is a configuration management concept so perpetually I have been there for some time there is something called Ansible there is Juju there is Source Stack and there is CFP engine and many more but I think these are the ones which are problematic to use in the market in terms of configuration management solutions CICV there is a standard I have used something called BitKite which was also as efficient as Jenkins in certain ways better flexible options than Jenkins BitPort, course control, Travis CI these are some of the open source that are available for your go through more slides and that's it I think I am done so this is for your monitoring solutions Nagios, CISMA, CometEars, Samsung, Monet if you want you can take a picture I am just starting short on that these are some of the loving poles which are open source solutions gridlock, lockstash, 4D, lockside, your Travis CI and some security I think that's the last one some security solution is on but no internet didn't have much basically after that so there were couple of security solutions that were available so if you want I am available outside you can always come back and talk to me because there is a requirement on DevOps, Cloud, Automation something that you want to consider if you are trying to implement those solutions you can copy of this one cool guys, thanks for having me here and it was nice having you and in practice with all of you hope there is some kind of take away from this session if you are not aware of DevOps at least now we have some clarity in case you know what is DevOps all about you have some maturity about it at least in terms of life cycle and those so that was the whole point of being here