Ansible Installation

 

Installation of Ansible on Centos 7

1. sudo -i

2. Open /etc/hostname and enter ansible.test.org for server and client.test.org for client machine

3. Also set hostname ansible.test.org; exit and sudo -i again on server

4. Also set hostname client.test.org; exit and sudo -i again on client

5. Edit /etc/hosts file on server and client and add the IP address and hostname of both on both server and client

172.31.21.33 ansible.test.org

172.31.23.202 client.test.org

6. Ping the client from server and server from client.

7. Create a user ‘test’ with password ‘test’ on both server and client VMs

useradd test

passwd test

8. We need to have this user run sudo commands without entering password. Open sudoers and add the following text:

vi /etc/sudoers

test ALL=(ALL) NOPASSWD: ALL

9. Save the file and run the following command to check test user is at the end of the result

cat /etc/passwd

10. Go to server and client terminals and run the following:

cd /etc/ssh

vi /etc/ssh/sshd_config

Remove # from these

PasswordAuthentication yes

PermitRootLogin yes

systemctl restart sshd

11. Let’s establish SSH connection by running this command on server and client

su test –login

12. We need to generate ssh certificates on server; press enter when prompted

ssh-keygen

ssh-copy-id test@client.test.org

ssh-copy-id test@ansible.test.org

13. Run the following command on server

ssh test@ansible.test.org

exit

ssh test@client.test.org

exit

14. Do all these steps on client also.

15. Now lets install Ansible on server and client VMs

sudo yum install -y epel-release

sudo yum install -y ansible

ansible --version

16. Now lets configure ansible hosts file on server

cd /etc/ansible

sudo mv hosts hosts.original

sudo vi hosts

[local]

ansible.test.org

[webserver]

client.test.org

17. Run the following command on server

ansible all -m ping

ansible all --list-hosts

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more