DevOps(Day-70): Ansible - Creating Inventory, Ansible Master-Node Configuration

 

  • Task-02: Creating Inventory

  • Task-03: Ansible Master-Node Configuration

  • Ansible Inventory - Ansible automates tasks on managed nodes or “hosts” in your infrastructure, using a list or group of lists known as inventory. You can pass host names at the command line, but most Ansible users create inventory files. Your inventory defines the managed nodes you automate, with groups so you can run automation tasks on multiple hosts at the same time. Once your inventory is defined, you use patterns to select the hosts or groups you want Ansible to run against.

    1. Create an inventory file in the below path and name the file as host.

      sudo nano /etc/ansible/hosts

    2. Before that, we need to create two Ansible node servers which will be connected to the Ansible master server.

    3. Assign the values in the file as shown in the below screenshot and save.

    4. Let's verify the inventory that we have created.

      ansible-inventory --list -y

  • Setup 2 more EC2 instances with the same Private keys as the previous instance (Node)

    We have created the two servers and set up the server to master the above task.

  • Copy the private key to the master server where Ansible is set up.

    1. Create a public key on the master server and copy the key using the ssh-keygen command.

    2. We can see id_rsa.pub which is the public key of the master server.

    3. Copy the above public key of the master to both the node server.

  • Try a ping command using Ansible to the Nodes.

    1. Now, use the ping command with the input of inventory file to it so that it will ping both the node servers.

    2. We can see both pings are successful which indicates servers are in active states.

Thanks for reading my article. Have a nice day

Comments

Post a Comment

Popular posts from this blog

DevOps(Day-97): Meta-Arguments in Terraform

Image
  TABLE OF CONTENTS Write about meta-arguments and their use in Terraform. Task-01: Meta-Arguments HandsOn Count for-each When you define a resource block in Terraform, by default, this specifies one resource that will be created. To manage several of the same resources, you can use either count or for_each, which removes the need to write a separate block of code for each one. Using these options reduces overhead and makes your code neater. count is what is known as a ‘meta-argument’ defined by the Terraform language. Meta-arguments help achieve certain requirements within the resource block. Write about meta-arguments and their use in Terraform. Meta-arguments in Terraform refer to a set of special arguments that can be used to define how a particular resource or module behaves within a Terraform configuration. These arguments provide additional configuration options and enable fine-grained control over the behaviour of resources or modules. Meta-arguments are prefixed with the...
Read more

DevOps(Day-95): Auto Scaling with Terraform

Image
  TABLE OF CONTENTS Understanding Scaling Pre-requisites Task 1: Create an Auto Scaling Group Task 2: Test Scaling Yesterday, we learned how to AWS S3 Bucket with Terraform. Today, we will see how to scale our infrastructure with Terraform. Understanding Scaling Scaling is the process of adding or removing resources to match the changing demands of your application. As your application grows, you will need to add more resources to handle the increased load. And as the load decreases, you can remove the extra resources to save costs. Terraform makes it easy to scale your infrastructure by providing a declarative way to define your resources. You can define the number of resources you need and Terraform will automatically create or destroy the resources as needed. Pre-requisites Create a  terraform.tf  file declaring the providers to be installed in the system according to the resources required. Create a  provider.tf  file to declare the region. Create a  vp...
Read more

DevOps (Day-1) Introduction

Image
  TABLE OF CONTENTS Infrastructure Automation Why DevOps is Important? What is DevOps? As the name indicates:- Dev + Ops = Development + Operations. Development i) Backend Developers ii) Front-end Developers iii) QA Operations i) System admins ii) Network admins iii) Database admins The practice of operations and development engineers participating together in the entire service lifecycle through a pipeline from design through the development process to production support. This process is known as DevOps. This is a process of automating the whole infrastructure. Now here comes a query, what are we automating? We are automating the whole team's work from the code-building stage to code deployment. Scenario 1:- In a company, there is a project in which developers are writing the code and deploying it to the QA environment frequently for each sprint. This code is then tested by the testing team. Suppose there is a situation of mishap happens where the testing team used the older code ...
Read more