What is DevOps || DevOps Tools
A free video tutorial from LevelUp360° DevOps | Google Cloud | Terraform | Kubernetes | Ansible
DevOps Professional Courses
4.4 instructor rating • 19 courses • 130,106 students
Learn more from the full courseDevOps MasterClass : Terraform Jenkins Kubernetes Ansible
DevOps with Jenkins Terraform AWS Docker Swarm Maven Kubernetes GIT & Ansible Automation with DevOps Realworld Exercises
53:38:33 of on-demand video • Updated October 2021
- An understanding of DevOps and the modern DevOps Tools Docker, Kubernetes, Jenkins, Docker Swarm, Kubernetes Helm.
- The ability as DevOps Engineer to Automate Code Delivery and Deployment Pipeline Using Jenkins.
- Complete Understanding of Docker Containers & Docker Swarm Orchestration & Kubernetes.
- Learn Building the Apps Dockerize using Docker Containers and Docker File & HELM as DevOps Engineer.
- Be DevOps Master in Kubernetes and Kubernetes Administration from Scratch to Advance Level.
- Kubernetes Development and Complete Deployment on Kubernetes & Docker Containers.
- As CI DevOps Engineer, Jenkins Multiple Integration with Modern Technology Tools like Docker, Code Delivery Pipeline, Git & GitHub .
English [Auto] Hello, team. Welcome back. Welcome to the club's training. This is the first lecture of dispirited locals. And today we will learn about what is gallops and what are the obstacles its. So we are going to cover these few topics in this particular lecture. We will learn by do we following the devil that this is right and what is the benefit of the wolf's practices? So first we learn about the evolution of software development over the years. Then we'll discuss a use case history of Facebook, which uses dev ops. Then we will learn what is dev ops. And at the end, we will learn about the different tool sets. It is used for that dev ops. So let's start with. So in the previous time order, you can see in the earlier time when software development started, though, there was different different kind of models, right? There was different different kinds of software development life cycles. So the most popular software development lifecycle was traditional waterfall model in the waterfall model. First, the request gather the requirement in the planning phase. Then we do the recording. Then we do the testing. Then maintenance. Right. So this is the complete product lifecycle of the traditional waterfall model. So every phase have their own significance. Right. So in the planning we was basically gathering the requirements after. Then we really started the development and after their development, we test the complete verdict. And after the test, we deployed the complete product and we use the maintenance. Right. So there was a different different kind of gaps available in that particular waterfall model as the product release lifecycle is very long. Right. Because we can't release the product until we built it completely. The testing effort is huge. The development of our it is also used because we are developing the complete verdict. And after then we are starting that testing. Right. We are not doing things independent. So DECT more than have these loopholes. So the next model which comes in the market is a zine devlopment in the US and development. The project, developed in feature, devised the Azal basically feature wise development in the product. We developed a single feature, right? We take the requirement DeBlois the feature tested and again go to the development if we are getting some kind of bugs. Once we complete single feature, we pick up the second feature. Right. So in the design development, we have a very short time delivery's. Height requirements in the Zile model requirements changes very frequently, developer needs to be first. But after the Zile now we are working in the area, which is called dev ops approaches. So dev ops approaches is best suited. Then we have the requirements is frequently devlopment needs to be a Zile and OPALESCENCE also needs to be assigned in the Dallas area. The devlopment and testing will continue in a single phase, right? We can develop and desk the product in parallel. Let us see how we can do that. So before move to the dev ops and Delfs technologies, first, I would like to share the experience of Facebook, which Facebook experienced in 2011. Right. So we know very well Facebook is a very big company. They hire the best engineers from the market site. They are also working on cutting edge technologies. And Facebook is example of the best enduring in the world. So Facebook launched few features in 2011. In 2011, Facebook introduced new features like timeline, music and ticker. Right. So in the last diagram, you can see where we have the word map. So we are showing over here the different different data centers of the Facebook like. These are the deployment jeunes of the Facebook. So when Facebook basically released these features in 2011, they deployed the new features on their all data centers. They basically released the new features worldwide in a single goal right after this. They faced some challenges. So basically, at the time of 2011, Facebook have 500 million users worldwide. Right. They used they released some new interesting features in their website, which attract a heavy traffic on the Facebook servers. And in the result, Facebook servers melted down. They stopped working. Right. And then the servers stopped working. There was the delay in the Facebook. There was a delay in the Facebook opening. There was a different, different kind of issues user experienced. So they got the mixed response from the user, which leads no conclusion because there is no way to remove these features. There's no way to come out from these kind of situations. Right. So after this, Facebook created a strategy which they called a dark launching technique. Right. So after this instant incident, Facebook comes with the dark launching technique. So let's discuss what is the dark launching technique? What is the strategy? Facebook maintains after the incident of 2011. So according to d'Arc launching technique, they basically divided the dog launching technique in three parts in the first bite. They discussed and they implemented a V like. New features are first deployed on a smaller and a specific user base. So instead of the complete user base, first, if we're introducing a new feature in our application, if we're going to deliver something new, then we will open that particular feature for a specific group or for a smaller group, which Google also used in the Google Check. First, Google Check was introduced in the company itself. Google checked was open for the Google employees only. Right. So the new feature will first deploy on a smaller area or on its model Jaune. Right. And it will be open for the specific user base. Right. Then they continuously monitor the feedbacks and continuously develop and tested. So basically, here we are getting to three new domes. First is the continuous monitoring. Second is continuous development. And third is continuous testing. These three dams are basically comes and develops. So when we are basically deploying a basic feature on a new feature to a specific group, we are monitoring the feedback of that particular feature. We are continuously developing the bugs. Okay. Which we are getting in that particular feature and testing and again, deploying. Right. So there is a cycle. We will discuss about this this particular cycle with a very good diagram in the coming slide. Right. Once the feature is a stable. Once we know that that particular feature is stable. Right. They are deployed on other user basis in multiple releases. So after the feature is a stable, we are still not going to deploy the complete feature or. All legal centres or what all are complete application. We will release it in multiple release for a specific specificly users supposed first we'll release it for the easier. Then we will release it for Europe. Then we will release it for America. Then we will release it for UK. Right. So we will release the new features in JUNK'S in multiple releases. So this is called a dart launching technique. So this is the diagram of the dark launching technique. So very first, the Facebook is a company which introduce a new feature, right? It will deploy when a specific user group, which is in the yellow bag. Right. And a specific data center. Then we get the get the bugs. So we will back the feature. So basically over here, we can see a cycle is being generated first. The feature is going to be specific user. We are getting the feedback, which is called continuous monitoring. If we get some kind of feedback, some bugs, then the feature again, go back to the development team. Right. They will fix it and test it. This is called continuous deployment development and communist testing. So feature is being released to a specific group. They are being monitored. If we are getting some bugs, they can go to the development team development team, fix and release a new build. It will again tested and again go to the development team. If there is a bug, so there is a complete cycle, which is called continuous monitoring companies development and condoms testing. Right. Once we have the feature is stable. Right. We will release that particular feature to our. Other users. This is called grumpiness indication, right? Once we have that part of the feature in our application, we will open that feature in multiple releases to multiple users. This is called continuous deployment. So we are deploying our application continuously on different different data centers or different different agents. So here, Velone, five new things. Right. So this is all basically the implementation of the dog launching technique. Are the activities or the fundamentals of that develops lifecycle? And Delfs lifecycle is all about the continuous deployment, communist devlopment, communist testing, Cartus integration and communist monitoring. Right. So this is the feed we just started that develops. Now we learn about their debt woes. So as we have already discussed, dev ops is not a technology, dev ops is not any programming language. So basically, dev ops is a software development approach. Right. Right. Waterfall model. Right. As a model develops is also a software development approach which involves companies development, continuous testing, continuous integration, continuous deployment and continuous monitoring of software throughout its development lifecycle. So it includes the plan. Good build test after test, Deb, like operate it and monitor it. If you are facing an issue, then again go to the plan. Good big test. And again, deploy abraded and monitary. This is a complete never ending cycle so that we have a sign like this, which is infinite design of their dev ops. So we're basically working in releases. We are planning something, cording that particular thing, developing that particular thing, build the project, tested again, deployed right after their deployment. We will operate it monitary. If we're getting any issues, we are getting any feedback. We again, go to the development phase. So this is a never ending cycle. But in that evolves, we have a very frequent releases, if you will. If you if you want, you can release your software weekly, biweekly, twice a month, thrice a month or in two months increments. So basically in the dev offs, we have a very frequent releases. This is the benefit of their dev ops approach. In this particular diagram, we are displaying some kind of tool sets which is required for that Arabs. So when we are talking about the plan and good, we can use some tools, acts like get right, like Severson and Jela device used for the defective boarding gate is used for the software version controls. And so some version is also used for this afterwards and control. We will discuss about the get the complete tutorials in the coming total and the coming videos. Then we will build our project. We have the different different kind of build tools available in the market. Like May one and and Cradle will use me when in this particular tutorial. Right. We will learn about them. Even if I will get the time, I will create the lectures on the griddle as well. Then next phase comes to the test and we have the testing tools like selenium. Jay, you need rest assured I. So here here you can see we have different differences and we have different different tools available for each feels right. Then we have the continuous deployment and monitoring for that. We have the tools like Ansible puppet chef Sarda Stack. Right. Then we have a communist monitoring and we have new RLC, Senso and Nadja's. This complete phase is basically called Daredevil's phase, and these are the tools of the Delfs profile or develops approaches. Right. So we are building the project. We are loving the project. We are building the project. We are testing it. We are applying it. Right. Monitoring it and again, building it. So this is the devil's. So that's all about the Dwarf's. If you have any questions regarding the things we have discussed today, then you can put your cushion in question and answer forum and I will answer your questions right in the coming tutorials. We will learn about the continuous deployment, communist integration, communist monitoring and about other ideas. Thank you. Thanks for your time.