How to setup Jenkins on Ubuntu using Ansible Role | Setup Java, Jenkins, Maven on Ubuntu EC2 using Ansible Role

Here below are the Ansible Roles for installing Java, Jenkins, Maven on Ubuntu EC2 instance using Ansible. You need to install Java first (first link below) and then do the steps in the second link for installing Jenkins, third link for installing Maven.

Click here if you would like to create a new Ubuntu EC2 instance using Ansible Playbook.

You can watch this lab on YouTube:

Pre-requisites:
Setup Ansible on your EC2 instance.

Java 11 Playbook
https://www.coachdevops.com/2024/02/ansible-role-for-java-11-installation.html

Jenkins Playbook
https://www.coachdevops.com/2024/02/install-jenkins-using-ansible-role-on.html

Maven Playbook
https://www.coachdevops.com/2024/02/install-maven-using-ansible-role-on.html

Create Ansible Role to create a new EC2 instance | Ansible Role for provisioning infrastructure in AWS | Refactor Ansible playbook into Ansible Role

We will learn how to create Ansible Role for provisioning a new EC2 instance in AWS cloud. We will pick a playbook which has all the logic and we will refactor into reusable ansible role.

What is Ansible Role?

Ansible also lets you organize tasks in a directory structure called a Role. Using Ansible roles you can break down complex playbooks into smaller and manageable chunks. Ansible role enables reuse and share our Ansible code efficiently.

How to create Ansible Role?

Using ansible galaxy command, we can create Ansible role. This will create the below directory with all the files. 

directory structure of Ansible role

aws-infra-role/

├── README.md

├── create.yml

├── defaults

│   └── main.yml

├── handlers

│   └── main.yml

├── meta

│   └── main.yml

├── tasks

│   ├── create-ec2.yml

│   └── create-sg.yml

├── tests

│   ├── inventory

│   └── test.yml

└── vars

    └── main.yml

Directory structure explained

tasks - contains the main list of tasks to be executed by the role.
handlers - handlers are typically used to start, reload, restart, and stop services.
defaults - default variables for the role.
vars - other variables for the role. Vars has the higher priority than defaults.
meta - defines some data / information about this role (author, dependency, versions, examples, etc,.)

tests - test cases if you have any.

Pre-requisites:

• Ansible is installed and Boto is also installed on Ubuntu EC2 instance
• Make sure you create an IAM role with AmazonEC2FullAccess policy and attach the role to EC2 instance.

Steps to create EC2 instance using Ansible Role:

Login to EC2 instance using Git bash or ITerm/putty where you installed Ansible. Execute the below command:

Create an Inventory file first

sudo mkdir /etc/ansible

Edit Ansible hosts or inventory file

sudo vi /etc/ansible/hosts

Add the below two lines in the end of the file:
[localhost]
local

cd ~
mkdir roles  

cd roles

Create Ansible Role

ansible-galaxy role init aws-infra-role

We will convert this playbook into ansible role.

So all the variables will go inside vars folder.

vars

    └── main.yml

sudo vi aws-infra-role/vars/main.yml

(copy below content)

keypair: myNov2023Key

instance_type: t2.small

image: ami-007855ac798b5175e

wait: yes

group: webserver

region: us-east-1

security_group: my-jenkins-security-grp1

Save the file and come out of it.

So all the tasks will go inside tasks folder. let's create security group first.

sudo vi aws-infra-role/tasks/create-sg.yml

---

  - include_vars: "vars/main.yml"

    tags: create

# tasks file for security group

  - name: configuring security group for the instance

    ec2_group:

        name: "{{ security_group }}"

        description: my-ajenkin-security_groAup

        region: "{{ region }}"

        rules:

            - proto: tcp

              from_port: 22

              to_port: 22

              cidr_ip: 0.0.0.0/0

            - proto: tcp

              from_port: 80

              to_port: 80

              cidr_ip: 0.0.0.0/0

            - proto: tcp

              from_port: 8080

              to_port: 8080

              cidr_ip: 0.0.0.0/0

        rules_egress:

            - proto: all

              cidr_ip: 0.0.0.0/0

Let's create a task for ec2 instance creation.

sudo vi aws-infra-role/tasks/create-ec2.yml

---

  - include_vars: "vars/main.yml"

    tags: create

  - name: creating ec2 instance

    ec2_instance:

        security_group: "{{ security_group }}"

        name: test-stan

        key_name: "{{ keypair }}"

        instance_type: "{{ instance_type}}"

        image_id: "{{ image }}"

        region: "{{ region }}"

        wait_timeout: 2   

Let's create a task for creating s3 bucket.

sudo vi aws-infra-role/tasks/create-s3.yml                                                                                                     ---

  - include_vars: "vars/main.yml"

    tags: create

  - name: creating s3

    s3_bucket:

      name: myansibles3bucket1234

      state: present

      region: "{{ region }}"

      versioning: yes

      tags:

        name: myansiblebucket

        type: example

    register: s3_url

  - name: Display s3 url

    debug: var=s3_url       

Let's create Ansible main playbook.

sudo vi aws-infra-role/main.yml

---

# This Playbook creates infra in aws cloud

- hosts: local

  connection: local

  gather_facts: False

  tags: ec2_create

  tasks:

  - include: tasks/create-sg.yml

  - include: tasks/create-ec2.yml

  - include: tasks/create-s3.yml 

now execute the ansible playbook by

ansible-playbook aws-infra-role/main.yml

If everything is good, you should see the new instance, S3 bucket created on AWS console. make sure you are able to connect to that instance.

That's it!! That is how you create a new EC2 instance using Ansible role in AWS cloud. 

Please watch steps in YouTube channel:

Install Ansible on Red Hat Linux | Setup Ansible on Red Hat Linux

How to setup Ansible on Red Hat Linux VM?

Ansible is #1 configuration management tool. It can also be used for infrastructure provisioning as well. or You can use Ansible in combination of Terraform which can take care of infra automation and Ansible can do configuration management. We will be setting up Ansible on Red Hat VM in Azure cloud And create some resources in AWS Cloud by using Ansible playbooks.

Ansible Architecture:

 

The best way to install Ansible in Linux is to use PIP, a package manager for Python.

Pre-requisites:

• Create new Red Hat EC2 in AWS Cloud for setting up Ansible, just open port 22 in firewall rule.

How to setup Ansible on Red Hat Linux VM?

Watch Steps in YouTube channel:

Change host name to AnsibleMgmtNode
sudo hostnamectl set-hostname AnsibleMgmtNode

Update Repository
sudo yum update -y

Install Python-pip3

sudo yum install python3-pip -y

Upgrade pip3 sudo pip3 install --upgrade pip

# Install Ansible pip3 install "ansible==2.9.17"

check Ansible version

ansible --version

Automate Azure cloud infrastructure setup using Ansible and Azure DevOps pipeline | How to integrate Ansible with Azure DevOps | Integrating Ansible with Azure DevOps Pipelines |

Ansible is an open-source, configuration management tool that automates cloud provisioning, configuration management, and application deployments. Using Ansible you can provision virtual machines, containers, network, and complete cloud infrastructures. 

Automate Azure cloud infrastructure setup using Ansible and Azure pipeline

Integrate Ansible with Azure Cloud

Integrating Ansible with Microsoft Azure allows you to automate and manage your Azure infrastructure using Ansible playbooks and modules. Ansible provides a collection of Azure-specific modules that enable you to provision and configure resources in Azure.

To configure Azure credentials, you need the following information:

• Your Azure subscription ID and tenant ID
• The service principal application ID and secret

Pre-requisites:

• Azure account subscription, click here if you don't have one.
• Service principal to create any resources in Azure cloud using Azure cloud shell or Azure CLI

Create Azure Service Principal

Run the following commands to create an Azure Service Principal:

az ad sp create-for-rbac --name <service-principal-name> \ 

--role Contributor \ 

--scopes /subscriptions/<subscription_id>

Save the above output in a file as you will not be able retrieve later.

Create an Ansible playbook

Create a simple playbook to create resource group in Azure. Make sure you modify the name of the resource group and location below.

---

- hosts: localhost

  connection: local

  tasks:

    - name: Creating resource group

      azure_rm_resourcegroup:

        name: "my-rg12"

        location: "eastus"

Create Azure YAML build pipeline:

Login to Azure Devops --> https://dev.azure.com

Select project dashboard.

Go to Pipelines -> New pipeline --> Click on Azure Repos Git or any SCM where you have playbooks stored. Select repo, click on Starter pipeline.

Add below four pipeline variables with value received from service principal creation.

AZURE_SUBSCRIPTION_ID

AZURE_CLIENT_ID

AZURE_SECRET

AZURE_TENANT

Add below tasks:

• Install Ansible on build agent
• Install Ansible rm module on build agent
• Execute Ansible playbook for creating resource group in Azure cloud.

trigger:

- main

pr: none # Disable PR triggers, can be adjusted as needed

pool:

vmImage: 'ubuntu-latest'

steps:

- script: |

# Install Ansible

pip3 install "ansible==2.9.17"

displayName: 'Install Ansible'

- script: |

# Install Ansible rm module

pip3 install ansible[azure]

displayName: 'Install Ansible rm module'

- script: |

# Run Ansible playbook to create resource group

ansible-playbook create-rg.yml

displayName: 'Run Ansible Playbook'

env:

AZURE_SUBSCRIPTION_ID: $(AZURE_SUBSCRIPTION_ID)

AZURE_CLIENT_ID: $(AZURE_CLIENT_ID)

AZURE_SECRET: $(AZURE_SECRET)

AZURE_TENANT: $(AZURE_TENANT)

Save the pipeline and run it.

Now Login to Azure cloud to see if the resource group have been created.

Watch Steps in YouTube channel:

Install Ansible on Red Hat Linux | How to setup Ansible on Red Hat Linux VM | Ansible install on Azure Linux Virtual Machine | Ansible Azure Integration

How to setup Ansible on Red Hat Linux VM and Integrate with Azure Cloud?

Ansible is #1 configuration management tool. It can also be used for infrastructure provisioning as well. or You can use Ansible in combination of Terraform which can take care of infra automation and Ansible can do configuration management. We will be setting up Ansible on Red Hat VM in Azure cloud And create some resources in Azure Cloud by using Ansible playbooks.

 

Ansible Architecture:

 

The best way to install Ansible in Linux is to use PIP, a package manager for Python.

Pre-requisites:

• Create new Red Hat VM in Azure Cloud for setting up Ansible, just open port 22 in firewall rule.
• Install Azure CLI on Red Hat Linus VM
• Service principal to create any resources in Azure cloud using Azure CLI

How to setup Ansible on Red Hat Linux VM

Watch Steps in YouTube channel:

Change host name to AnsibleMgmtNode
sudo hostnamectl set-hostname AnsibleMgmtNode

Update Repository
sudo yum update -y

Install Python-pip3

sudo yum install python3-pip -y

Upgrade pip3 sudo pip3 install --upgrade pip

# Install Ansible pip3 install "ansible==2.9.17"

check Ansible version

ansible --version

# Install Ansible azure_rm module for interacting with Azure.

pip3 install ansible[azure]

Authenticate with Azure

To configure Azure credentials, you need the following information:

• Your Azure subscription ID and tenant ID
• The service principal application ID and secret

Create an Azure Service Principal

Login to Azure first

az login

Enter Microsoft credentials

Run the following commands to create an Azure Service Principal:

az ad sp create-for-rbac --name <service-principal-name> \ 

--role Contributor \ 

--scopes /subscriptions/<subscription_id>

Save the above output in a file as you will not be able retrieve later.
Configure the Ansible credentials using one of the following techniques:

• Option 1: Create an Ansible credentials file

• Option 2: Define Ansible environment variables

Option 1: Create Ansible credentials file

In this section, you create a local credentials file to provide credentials to Ansible. For security reasons, credential files should only be used in development environments.

mkdir ~/.azure 

vi ~/.azure/credentials

Insert the following lines into the file. Replace the placeholders with the service principal values.

[default] subscription_id=<subscription_id> client_id=<service_principal_app_id> secret=<service_principal_password> tenant=<service_principal_tenant_id>

Option 2: Define Ansible environment variables

On the host virtual machine, export the service principal values to configure your Ansible credentials.

export AZURE_SUBSCRIPTION_ID=<subscription_id> export AZURE_CLIENT_ID=<service_principal_app_id> export AZURE_SECRET=<service_principal_password> export AZURE_TENANT=<service_principal_tenant_id>

Test Ansible installation

You now have a virtual machine with Ansible installed and configured!

This section shows how to create a test resource group within your new Ansible configuration. If you don't need to do that, you can skip this section.

• Option 1: Use an ad-hoc ansible command
• Option 2: Write and run an Ansible playbook

Option 1: Use an ad-hoc ansible command

Run the following ad-hoc Ansible command to create a resource group:

ansible localhost -m azure_rm_resourcegroup -a "name=my-rg123 location=eastus"

Option 2: Write and run an Ansible playbook

Create a simple playbook to create resource group in Azure.

sudo vi create-rg.yml

---

- hosts: localhost

  connection: local

  tasks:

    - name: Creating resource group

      azure_rm_resourcegroup:

        name: "myResourceGroup"

        location: "eastus"

Execute the playbook using ansible-playbook command.

ansible-playbook create-rg.yml

Now Login to Azure cloud to see if the resource group have been created.

Clean up Resources

Save the following code as delete-rg.yml

sudo vi delete-rg.yml

--- - hosts: localhost tasks: - name: Deleting resource group - "{{ name }}" azure_rm_resourcegroup: name: "{{ name }}" state: absent register: rg - debug: var: rg

ansible-playbook delete-rg.yml --extra-vars "name=myResourceGroup"

check in Azure cloud to see if the resource group have been deleted.