DevOps Training Video | Infrastructure as Code Explained | DevOps Tutorial for Beginners - Part 5 HD

DevOps Training Video | Infrastructure as Code Explained | DevOps Tutorial for Beginners - Part 5 https://goo.gl/o768rn Hello Everyone! Welcome back to the DevOps course from AcadGild. In this session, we are going to discuss the 5th module of DevOps Training i.e. IAC, (Infrastructure as Code). If you have missed the previous sessions, please check the links as follows, Introduction to DevOps: https://www.youtube.com/watch?v=dMILqmX_xEk DevOps Infrastructure: https://www.youtube.com/watch?v=X6gpBj4RyKk&t=12s Version Control Systems: https://www.youtube.com/watch?v=Klfjr4TF9i0 Continuous Integration Management: https://www.youtube.com/watch?v=XXRud7KWVU4&t=25s As a DevOps professional, you have probably heard of IAC or configuration management before, along with tools like Puppet, Ansible, Chef, CFEngine, and SaltStack. In this video, we shall discuss these tools to understand what they are, and how they’re useful to us. Let’s start with the basics. What is IAC? IAC, or Infrastructure as Code, enables us to manage and configure our physical and virtual machines programmatically. Say, we have five servers. Each of these servers are configured in a certain way. So for example, in server one, we have Git. In server two, we have Jenkins. Server three has Tomcat. Server four is for the database. And lastly, server five have Nagios running on it. Now, in order for these applications to work effectively and serve the users right, we need to not only install the applications but also their correct configurations on the servers. For instance, we might have to create some config files for Git. In case of Jenkins, we’ll need to install some config files along with tools like Java, which are required for Jenkins. Additionally, we may also have to create some users for Jenkins. Similarly, Tomcat requires Java, users, and some management. Database and Nagios would also have its own requirements. If we’re managing a small set of servers, the task is fairly easy. We can manage it manually. Whenever there is a requirement, we log in to change the configuration and meet the requirement. If we have to change something on the Tomcat server, we can login to the machine, perform the required task, and our service will be up and running again. But what if, we have five Git servers and ten Jenkins machines, or a hundred database servers. What do we do in such scenarios? How do we manage such big infrastructures? In such situations, when the infrastructure is large and the task difficult, it makes more sense for us to manage it programmatically. That is, we need to figure out a way to define and control the configuration of all servers from a single location. The solution lies in configuration management, which is also known as IAC - Infrastructure as Code. There are a number of tools that allow us to achieve this goal. But before we get into them, let us try and delve a little deeper into the advantages of using these tools. The first advantage is fairly obvious