CentOS-Linux4U: On-Prem DevOps Infrastructure Project (2026 Edition)

In this project, we will design and implement a complete on-premises IT infrastructure within a home lab environment. The objective is to simulate a real-world enterprise setup that includes virtualization, server administration, automation, monitoring, patch management, and performance testing.

This project will cover the following key areas:

Installation and management of Windows and Linux servers
Deployment of Linux servers on VMware ESXi hosts
Centralized management using VMware vCenter
Server provisioning and configuration using Ansible and Terraform
Automation of administrative tasks using Ansible and Puppet
Monitoring of Linux and Windows servers with Zabbix, Prometheus and Grafana
OS patching and upgrade management
Stress testing and performance analysis

The purpose of this project is to maintain hands-on experience across VMware technologies, Linux administration, and modern DevOps practices within a controlled lab environment.

Host System Configuration

The entire lab environment is built on the following desktop system and below details:

Device Name: win01
Processor: AMD FX™-8350 Eight-Core Processor @ 4.00 GHz
Installed RAM: 32.0 GB (31.5 GB usable)
Operating System: Windows 10 Pro
Virtualization Platform: VMware® Workstation 16 Pro

VMware Workstation is used to create and manage nested virtualization environments, including VMware ESXi hosts and other virtual machines.

Virtual Machines in the Lab

The following virtual machines will be created on VMware® Workstation 16 Pro:

1. win01

Hardware Details: CPU 1, RAM 2 GB, Disk 60GB / 10GB, 2 NIC
OS Details: Windows 2019 Datacenter Desktop Edition

2. esxi01

Hardware Details: CPU 2, RAM 14GB, Disk 1000GB, 2 NIC
OS Details: VMware ESXi 7.0.3

3. esxi02

Hardware Details: CPU 2, RAM 8GB, Disk 1000GB, 2 NIC
OS Details: VMware ESXi 7.0.3

4. kub01

Hardware Details: CPU 2, RAM 4GB, Disk 40GB, 2 NIC
OS Details: Ubuntu 18

5. kub02

Hardware Details: CPU 1, RAM 2GB, Disk 40GB, 2 NIC
OS Details: Ubuntu 18

We are going to create two networks on VMware® Workstation 16 Pro:

Host-Only network (172.16.0.0/16) for internal communication and optimal performance.
Bridged network (192.168.2.0/24) for external communication, such as accessing the internet and downloading software.

Task 1. Installation and configuration of Windows Server 2019 on VMWare WorkStation 16 pro.

1. We initiated the installation of Windows Server 2019 Datacenter Desktop Edition on win01.

2. We renamed the hostname to "win01."

3. We assigned the following IP addresses:

Internal IP address: 172.16.1.200
External IP address: 192.168.2.200

4. The firewall was disabled.

5. We configured Active Directory and set the domain to "darole.org."

The Windows Server 2019 installation and configuration on win01 have been completed as outlined above.

Task 2. Add A and MX records to DNS hosted on win01.

We recognize the importance of DNS for the proper functioning of VMware vCenter, and as there are two networks in use, we will configure DNS to optimize communication via the internal network for improved performance. Additionally, we will configure MX records to facilitate sending and receiving emails.

A Record Details:

For Container Orchestration:

172.16.1.230 kub01.darole.org
172.16.1.231 kub02.darole.org
172.16.1.240 dock01.darole.org

For VMs:

172.16.1.211 lamp01.darole.org
172.16.1.212 zap01.darole.org
172.16.1.213 pup01.darole.org
172.16.1.221 web01.darole.org
172.16.1.222 db01.darole.org
172.16.1.223 ans01.darole.org
172.16.1.252 jen01.darole.org
172.16.1.253 son01.darole.org
172.16.1.241 gra01.darole.org

For Websites:

172.16.1.215 ninom.darole.org
172.16.1.216 online-education.darole.org
172.16.1.217 organic-farm.darole.org
172.16.1.225 jobsearch.darole.org
172.16.1.218 travel.darole.org
172.16.1.219 jewellery.darole.org
172.16.1.220 carvilla.darole.org

For VMware:

172.16.1.205 esxi01.darole.org
172.16.1.206 esxi02.darole.org
172.16.1.207 vcenter01.darole.org
172.16.1.200 win01.darole.org

MX Record Details:

172.16.1.213 pup01.darole.org

Automating DNS Entry Creation Using PowerShell

PS C:\scripts> cat update-dns.ps1

# DNS Server and Zone

$dnsServer = "localhost"

$zoneName = "darole.org"

# DNS Records

$records = @(

@{Name="ans01"; IP="172.16.1.223"}

@{Name="db01"; IP="172.16.1.222"}

@{Name="dock01"; IP="172.16.1.240"}

@{Name="esxi01"; IP="172.16.1.205"}

@{Name="esxi02"; IP="172.16.1.206"}

@{Name="jen01"; IP="172.16.1.252"}

@{Name="jobsearch"; IP="172.16.1.225"}

@{Name="kub01"; IP="172.16.1.230"}

@{Name="kub02"; IP="172.16.1.231"}

@{Name="lamp01"; IP="172.16.1.211"}

@{Name="ninom"; IP="172.16.1.215"}

@{Name="online-education"; IP="172.16.1.216"}

@{Name="organic-farm"; IP="172.16.1.217"}

@{Name="pup01"; IP="172.16.1.213"}

@{Name="tomd01"; IP="172.16.1.250"}

@{Name="tomp01"; IP="172.16.1.251"}

@{Name="vcenter01"; IP="172.16.1.207"}

@{Name="web01"; IP="172.16.1.221"}

@{Name="win01"; IP="192.168.2.200"}

@{Name="win01"; IP="172.16.1.200"}

@{Name="zap01"; IP="172.16.1.212"}

@{Name="son01"; IP="172.16.1.253"}

@{Name="gra01"; IP="172.16.1.241"}

)

foreach ($record in $records) {

$name = $record.Name

$ip = $record.IP

$existing = Get-DnsServerResourceRecord -ZoneName $zoneName -Name $name -ErrorAction SilentlyContinue

if ($existing) {

Write-Host "Updating $name -> $ip"

Remove-DnsServerResourceRecord -ZoneName $zoneName -RRType "A" -Name $name -Force

}

Add-DnsServerResourceRecordA -Name $name -ZoneName $zoneName -IPv4Address $ip

}

PS C:\scripts>

Script Execution Output

PS C:\scripts> .\update-dns.ps1

Updating ans01 -> 172.16.1.223

Updating db01 -> 172.16.1.222

Updating dock01 -> 172.16.1.240

Updating esxi01 -> 172.16.1.205

Updating esxi02 -> 172.16.1.206

Updating jen01 -> 172.16.1.252

Updating jobsearch -> 172.16.1.225

Updating kub01 -> 172.16.1.230

Updating kub02 -> 172.16.1.231

Updating lamp01 -> 172.16.1.211

Updating ninom -> 172.16.1.215

Updating online-education -> 172.16.1.216

Updating organic-farm -> 172.16.1.217

Updating pup01 -> 172.16.1.213

Updating tomd01 -> 172.16.1.250

Updating tomp01 -> 172.16.1.251

Updating vcenter01 -> 172.16.1.207

Updating web01 -> 172.16.1.221

Updating win01 -> 192.168.2.200

Updating win01 -> 172.16.1.200

Updating zap01 -> 172.16.1.212

Updating son01 -> 172.16.1.253

Updating gra01 -> 172.16.1.241

PS C:\scripts>

Key Benefits of Automation

Saves time (bulk DNS creation in seconds)
Avoids manual errors
Easy to update or re-run
Scalable for large environments

Task 3: ESXi Host Deployment and Configuration on VMware WorkStation.

In this step, we will deploy VMware ESXi hosts on top of VMware Workstation using nested virtualization. This setup helps simulate a real enterprise data center environment within a home lab.

What is VMware ESXi?

VMware ESXi is a bare-metal (Type-1) hypervisor that allows you to run multiple virtual machines (VMs) on a single physical system. It is widely used in enterprise environments for virtualization.

For this lab, we are using the free version of ESXi, which is ideal for learning, testing, and small-scale deployments.

Key Features of ESXi Free

No Licensing Cost – Available for free, suitable for lab environments
Easy Management – Web-based UI for managing virtual machines
Efficient Resource Usage – Supports multiple VMs on a single host
Stable & Reliable – Used globally in production environments

We deployed two ESXi hosts inside VMware Workstation

ESXi Host 1: esxi01.darole.org

CPU: 2 Cores with Virtualization enabled.
RAM: 14 GB.
Disks: 1000 GB.
Internal IP: 172.16.1.205.
Host Name: esxi01.darole.org.
OS: VMware ESXi 7.0.3

ESXi Host 2: esxi02.darole.org

CPU: 2 Cores with Virtualization enabled.
RAM: 8 GB.
Disks: 1000 GB.
Internal IP: 172.16.1.206.
Host Name: esxi02.darole.org.
OS: VMware ESXi 7.0.3.

After the installation is complete, log in to win01 and check esxi01 and esxi02 through the web console.

Web Console Login Details:

User Name: root

Password: Pass@1234

Ensure that you have access to both esxi01 and esxi02 via the web console using the provided login credentials. This step is essential for further configuration and management of your ESXi hosts.

Task 4. Deploying the vCenter Server Appliance on esxi01.

In this step, we will deploy the vCenter Server Appliance (VCSA) on esxi01. vCenter provides centralized management for ESXi hosts, allowing us to manage clusters, virtual machines, networking, and storage from a single interface.

Prerequisites

Before starting the deployment, ensure the following requirements are met for a Tiny Environment:

vCPU: 2
Memory: 12 GB
Storage: 1000 GB

Proper DNS configuration is critical for vCenter deployment. Verify that the hostname resolves correctly from win01:

C:\Users\Administrator>nslookup vcenter01.darole.org
Server: localhost
Address: 127.0.0.1

Name: vcenter01.darole.org
Address: 172.16.1.207

C:\Users\Administrator>

Step A. Add the VMware-VMvisor-Installer-7.0.0-15843807.x86_64.iso image to win01.

Step B. Navigate to the `vcsa-ui-installer\win32` directory on the mounted disk and run `installer.exe`.

Step C. There are two stages in the deployment process:

Stage 1 - Deploy vCenter Server.

Select deployment target (esxi01)
Configure VM name, storage, and network settings

Stage 2 - Set up vCenter Server.

Configure:

SSO domain (vsphere.local)
Administrator password
Networking & time settings

Step D. After completing the installation, log in to the web console for VMware Appliance Management at:

URL: https://vcenter01.darole.org:5480
User Name: administrator@vsphere.local
Password: Pass@1234

Step E. In the vCenter Server web console, navigate to:

URL: https://vcenter01.darole.org
User Name: administrator@vsphere.local
Password: Pass@1234

Step F. Create a datacenter named "darole-dc" and a cluster named "my-cluster."

Step G. Add the ESXi hosts esxi01 and esxi02 to the cluster.

Start & Stop vCenter

To start vCenter, log in to the console of esxi01 and start the vCenter VM.
To stop vCenter, log in to the appliance configuration and choose the shutdown option.

Important Note: Use the Internat network (172.16.0.0) for vCenter installation. Using the external network (192.168.2.0) for vCenter installation may lead to failures due to network issues.

For more detailed instructions, you can refer to the provided link: [VMware vSphere 7 Installation Setup](https://www.nakivo.com/blog/vmware-vsphere-7-installation-setup/)

Follow these steps carefully to ensure a successful deployment of the vCenter Server Appliance on esxi01.

Task 5. Virtual networking setup on VCenter01.

Now that the vCenter is successfully deployed, the next stop is to configure virtual networking for both ESXi hosts

Add multiple NICs
Separate Internal and external traffic
Configure NIC Teaming for better performance and redundancy

Objective:

Use Host-Only network (172.16.x.x) for internal communication
Use Bridged network (192.168.2.x) for external access
Improve performance using NIC teaming

Configuration for esxi01:

1.Shutdown esxi01.

2. Add 3 extra network cards to esxi01:

Ethernet 2: Host-Only (for internal communication)
Ethernet 3: Bridge (for external communication)

3. Start esxi01.

4. Start the vCenter.

5. Once the vCenter is created, go to esxi01:

Navigate to "Configure" -> "Networking."

6. Add 2 NICs to the existing internat network (switch0).

Internal Network IP: 172.16.1.205 (teaming of 3 NICs)

7. Create a new switch for the external network and add the pending NIC (bridge).

External Network IP: 192.168.2.205 (only 1 NIC)

Configuration for esxi02:

1. Shutdown esxi02.

2. Add 3 extra network cards to esxi02:

Ethernet 2: Host-Only (for internal communication)
Ethernet 3: Bridge (for external communication)

3. Start esxi02.

4. Start the vCenter.

5. Once the vCenter is created, go to esxi02:

Navigate to "Configure" -> "Networking."

6. Add 2 NICs to the existing internet network (switch0).

Internal Network IP: 172.16.1.206 (teaming of 3 NICs)

7. Create a new switch for the external network and add the pending NIC (bridge).

External Network IP: 192.168.2.206 (only 1 NIC)

After the network configuration is complete, check if both esxi hosts are accessible from the external network:

http://192.168.2.205 for esxi01

http://192.168.2.206 for esxi02

Ensure that the networking changes have been applied correctly, and you can access both hosts externally as specified.

Task 6. Create ISO store and VM templates.

In this step, we will prepare our environment for quick and consistent VM deployment by:

Uploading ISO files to datastore
Creating base virtual machines
Converting them into templates

This is an important step for automation and scaling in any DevOps environment.

What is Datastore:

A datastore in vCenter is a centralized storage location where virtual machines' files are stored. It can be a SAN, NAS, or local storage. Datastores hold virtual machine files, ISO images, templates, and snapshots

What is Template:

A template in vCenter is a master copy of a virtual machine that can be used to create multiple identical VMs quickly. They help maintain consistency and reduce manual setup efforts when creating new VMs.

Step 1: Uploading ISO Images to ESXi02

As our vCenter is running on ESXi01 and is experiencing high loads, we'll upload ISO images to ESXi02 for better resource distribution. We'll place the ISO files in the /iso folder within the ESXi02 datastore.

Upload the following OS images:

Ubuntu 24.04
Rocky 8.7
Red Hat 8.5

Step 2: Create Rocky Linux VM

Hostname: rocky
CPU: 1
Memory: 2 GB
Disk: 16 GB
Internal IP: 172.16.1.228
External IP: 192.168.2.228
user root
password redhat

Step 3: Create Red Hat VM

Hostname: redhat
CPU: 1
Memory: 1 GB
Disk: 16 GB
Internal IP: 172.16.1.226
External IP: 192.168.2.226
user root
password redhat

Step 4: Create Ubuntu VM

Hostname: ubuntu
CPU: 1
Memory: 2 GB
Disk: 16 GB
Internal IP: 172.16.1.227
External IP: 192.168.2.227
user vallabh
password redhat

Step 5: Convert VMs into Templates

Right-click on VM
Select Template → Convert to Template

Benefits of Using Templates

Faster VM deployment
Standardized configuration
Reduced manual errors
Ideal for automation (Terraform / Ansible)

Task 7. Infrastructure Automation with Terraform

In this step, we introduce Infrastructure as Code (IaC) using Terraform to automate VM deployment on vCenter.

Instead of creating virtual machines manually, Terraform allows us to provision infrastructure in a consistent and repeatable way.

Objective

Install Terraform on win01
Connect Terraform to vCenter
Deploy one test VM (ans01-vm) using a template
Keep remaining VM automation for the next phase

Step 1: Install Terraform

Download Terraform from the official website
Extract it to:

C:\terraform-vsphere

Add Terraform to system PATH

Verify Installation

terraform -version

 Step 2: Create Terraform Configuration File

Create a file named: main.tf

This file will define:

vCenter connection
Datacenter and datastore
Template to clone from
VM configuration

C:\terraform-vsphere> cat main.tf


provider "vsphere" {
  user           = "administrator@vsphere.local"
  password       = "Pass@1234"
  vsphere_server = "vcenter01.darole.org"

  allow_unverified_ssl = true
}

data "vsphere_datacenter" "dc" {
  name = "darole-dc"
}

data "vsphere_datastore" "datastore" {
  name          = "datastore1"
  datacenter_id = data.vsphere_datacenter.dc.id
}

data "vsphere_compute_cluster" "cluster" {
  name          = "my-cluster"
  datacenter_id = data.vsphere_datacenter.dc.id
}

data "vsphere_network" "network" {
  name          = "VM Network"
  datacenter_id = data.vsphere_datacenter.dc.id
}

data "vsphere_virtual_machine" "template" {
  name          = "ubuntu-template"
  datacenter_id = data.vsphere_datacenter.dc.id
}

resource "vsphere_virtual_machine" "ans01" {
  name             = "ans01-vm"
  resource_pool_id = data.vsphere_compute_cluster.cluster.resource_pool_id
  datastore_id     = data.vsphere_datastore.datastore.id

  num_cpus = 1
  memory   = 1024
  guest_id = data.vsphere_virtual_machine.template.guest_id

  network_interface {
    network_id   = data.vsphere_network.network.id
    adapter_type = "vmxnet3"
  }

  disk {
    label            = "disk0"
    size             = 16
    thin_provisioned = true
  }

  clone {
    template_uuid = data.vsphere_virtual_machine.template.id
  }
}

Step 3: Run Terraform Commands

Navigate to the Terraform directory:

C:\terraform-vsphere

Run the following commands:

terraform init

terraform plan

terraform apply

Type yes when prompted.

Output

A new VM ans01-vm will be created in vCenter
VM will be cloned from the template
No manual intervention required

Task 8: Ansible Server Configuration (ans01)

This section describes the setup of the Ansible server (ans01) and automation tasks used for VM deployment in the environment.

1. Creating and Configuring Ansible Server

A new VM ans01 was created from the Ubuntu template.

Configuration performed:

Hostname set to ans01.darole.org
Two IP addresses configured

172.16.1.223
192.168.2.223

Firewall disabled

Commands


# hostnamectl set-hostname ans01.darole.org

Network Configuration


# cat /etc/netplan/00-installer-config.yaml
network:
    version: 2
    ethernets:
        ens192:
            addresses:
            - 192.168.2.223/24
            gateway4: 192.168.2.1
            nameservers:
                addresses:
                - 192.168.2.1
        ens160:
            addresses:
            - 172.16.1.223/16


# systemctl disable ufw
# reboot

2. Updating the Server


# apt update
# apt upgrade -y
# reboot

Note: Ensure sufficient disk space before upgrading.

3. Installing Ansible and Dependencies

Update repositories:


root@ans01:~# apt update

Install Python dependencies:


root@ans01:~# apt install python3-full python3-venv -y

Create Python virtual environment:


root@ans01:~# python3 -m venv vmware-env
source vmware-env/bin/activate

Install required packages:


(vmware-env) root@ans01:~# pip install pyvmomi
(vmware-env) root@ans01:~# python -c "import pyVmomi; print('pyVmomi installed')"
(vmware-env) root@ans01:~# pip install ansible
(vmware-env) root@ans01:~# pip install requests
(vmware-env) root@ans01:~# ansible-galaxy collection install community.vmware

4. Using Ansible Playbooks for VM Creation

Clone playbook repository:


(vmware-env) root@ans01:~# mkdir /git-data ; cd /git-data
(vmware-env) root@ans01:~# git clone https://github.com/vdarole/ansible.git

Navigate to project directory:


(vmware-env) root@ans01:~# cd ansible
(vmware-env) root@ans01:~# cp hosts /etc/
(vmware-env) root@ans01:~# cd vmware

Edit variables file:


(vmware-env) root@ans01:~# vi vars.yml

vars.yml


---
vcenter_hostname: "vcenter01.darole.org"
vcenter_username: "administrator@vsphere.local"
vcenter_password: "Pass@1234"
vm_name: "<VM Name>"
template_name: "<template Name>"
virtual_machine_datastore: "esxi02-datastore1"
vcenter_validate_certs: false
cluster_name: "my-cluster"
vcenter_datacenter: "darole-dc"
vm_folder: "<VM Name>"
vm_disk_gb: 2
vm_disk_type: "thin"
vm_disk_datastore: "esxi02-datastore1"
vm_disk_scsi_controller: 1
vm_disk_scsi_unit: 1
vm_disk_scsi_type: "paravirtual"
vm_disk_mode: "persistent"

Run playbook:


(vmware-env) root@ans01:~# ansible-playbook create-vm.yml

5. VM Creation Details

Templates used:

Rocky Template

pup01-vm
jen01-vm
son01-vm
zap01-vm

RedHat Template

lamp01-vm
web01-vm
db01-vm

Ubuntu Template

dock01-vm
tomp01-vm
tomd01-vm
gra01-vm

6. VM Migration

The following VMs were migrated from esxi02 to esxi01:

tomp01-vm
zap01-vm
jen01-vm
dock01-vm
gra01-vm
web01-vm
db01-vm

7. Repository

All Ansible playbooks are stored in the GitHub repository:


https://github.com/vdarole/ansible

Note: VM names include -vm suffix because the ESXi hosts will later be monitored using Zabbix monitoring tool.

Task 9. Configuring Hostname and IP Address for New VMs

In our ongoing project to set up an extensive IT infrastructure, we have now successfully created several virtual machines (VMs) in previous task. To make these VMs fully functional, it's essential to assign them proper hostnames and IP addresses. In this blog post, we'll walk you through the configuration steps for four different types of VMs: Rocky, Red Hat, and Ubuntu.

Rocky VMs

1. pup01.darole.org

CentOS VMs are known for their compatibility with the CentOS repository, making software management straightforward.

Set the hostname

# hostnamectl set-hostname pup01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces

# sed -i 's/172.16.1.228/172.16.1.213/g' /etc/sysconfig/network-scripts/ifcfg-ens192

# sed -i 's/192.168.2.228/192.168.2.213/g' /etc/sysconfig/network-scripts/ifcfg-ens224

Disable SELinux and the firewall

# sed -i 's/enforcing/disabled/g' /etc/selinux/config

# systemctl disable firewalld

Reboot to apply changes

# reboot

2. zap01.darole.org

Follow the same steps as for pup01.darole.org but with different IP addresses:

Set the hostname

# hostnamectl set-hostname zap01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces

# sed -i 's/172.16.1.228/172.16.1.212/g' /etc/sysconfig/network-scripts/ifcfg-ens192

# sed -i 's/192.168.2.228/192.168.2.212/g' /etc/sysconfig/network-scripts/ifcfg-ens224

Disable SELinux and the firewall

# sed -i 's/enforcing/disabled/g' /etc/selinux/config

# systemctl disable firewalld

Reboot to apply changes

# reboot

3. jen01.darole.org

Follow the same steps as for pup01.darole.org but with different IP addresses:

Set the hostname

# hostnamectl set-hostname jen01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces

# sed -i 's/172.16.1.228/172.16.1.252/g' /etc/sysconfig/network-scripts/ifcfg-ens192

# sed -i 's/192.168.2.228/192.168.2.252/g' /etc/sysconfig/network-scripts/ifcfg-ens224

Disable SELinux and the firewall

# sed -i 's/enforcing/disabled/g' /etc/selinux/config

# systemctl disable firewalld

Reboot to apply changes

# reboot

4. son01.darole.org

Follow the same steps as for pup01.darole.org but with different IP addresses:

Set the hostname

# hostnamectl set-hostname son01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces

# sed -i 's/172.16.1.228/172.16.1.253/g' /etc/sysconfig/network-scripts/ifcfg-ens192

# sed -i 's/192.168.2.228/192.168.2.253/g' /etc/sysconfig/network-scripts/ifcfg-ens224

Disable SELinux and the firewall

# sed -i 's/enforcing/disabled/g' /etc/selinux/config

# systemctl disable firewalld

Reboot to apply changes

# reboot

Red Hat VMs

1. lamp01.darole.org

Red Hat VMs require attaching a Red Hat subscription for package management. Here are the steps for hostname and IP address configuration:

Set the hostname

# hostnamectl set-hostname lamp01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces

# sed -i 's/172.16.1.226/172.16.1.211/g' /etc/sysconfig/network-scripts/ifcfg-ens192

# sed -i 's/192.168.2.226/192.168.2.211/g' /etc/sysconfig/network-scripts/ifcfg-ens224

Disable SELinux and the firewall

# sed -i 's/enforcing/disabled/g' /etc/selinux/config

# systemctl disable firewalld

Reboot to apply changes

# reboot

Register with Red Hat and attach a subscription

# subscription-manager register

Registering to: subscription.rhsm.redhat.com:443/subscription

Username: daroleapeksha

Password:

The system has been registered with ID: 76ad51ff-3595-4f71-91e8-6d8dd2105d17

The registered system name is: lamp01.darole.org

2. web01.darole.org

Follow the same steps as for lamp01.darole.org but with different IP addresses and hostname:

Set the hostname

# hostnamectl set-hostname web01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces

# sed -i 's/172.16.1.226/172.16.1.221/g' /etc/sysconfig/network-scripts/ifcfg-ens192

# sed -i 's/192.168.2.226/192.168.2.221/g' /etc/sysconfig/network-scripts/ifcfg-ens224

Disable SELinux and the firewall

# sed -i 's/enforcing/disabled/g' /etc/selinux/config

# systemctl disable firewalld

Reboot to apply changes

# reboot

Register with Red Hat and attach a subscription

# subscription-manager register

Registering to: subscription.rhsm.redhat.com:443/subscription

Username: daroleapeksha

Password:

The system has been registered with ID: c1d559a1-4b99-4918-9a9c-923b93df2e2a

The registered system name is: web01.darole.org

3. db01.darole.org

Follow the same steps as for web01.darole.org but with different IP addresses and hostname:

Set the hostname

# hostnamectl set-hostname db01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces

# sed -i 's/172.16.1.226/172.16.1.222/g' /etc/sysconfig/network-scripts/ifcfg-ens192

# sed -i 's/192.168.2.226/192.168.2.222/g' /etc/sysconfig/network-scripts/ifcfg-ens224

Disable SELinux and the firewall

# sed -i 's/enforcing/disabled/g' /etc/selinux/config

# systemctl disable firewalld

Reboot to apply changes

# reboot

Register with Red Hat and attach a subscription

# subscription-manager register

Registering to: subscription.rhsm.redhat.com:443/subscription

Username: daroleapeksha

Password:

The system has been registered with ID: cdaa2a9b-fa30-4452-93b5-9cf85f9917e1

The registered system name is: db01.darole.org

Ubuntu VM

1. dock01.darole.org

Ubuntu VMs are known for their ease of use with the Ubuntu repository. Here's how to configure hostname and network:

Set the hostname

# hostnamectl set-hostname dock01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces using Netplan

# cat /etc/netplan/50-cloud-init.yaml

network:

version: 2

ethernets:

ens192:

addresses:

- 192.168.2.240/24

gateway4: 192.168.2.1

nameservers:

addresses:

- 192.168.2.1

ens160:

addresses:

- 172.16.1.240/16

- 172.16.1.215/16

- 172.16.1.216/16

- 172.16.1.217/16

- 172.16.1.218/16

- 172.16.1.219/16

- 172.16.1.220/16

Disable the Uncomplicated Firewall (UFW)

# systemctl disable ufw

Reboot to apply changes

# reboot

2. kub01.darole.org

Set the hostname

# hostnamectl set-hostname kub01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces using Netplan

# cat /etc/netplan/00-installer-config.yaml

network:

version: 2

ethernets:

ens32:

addresses:

- 192.168.2.230/24

gateway4: 192.168.2.1

nameservers:

addresses:

- 192.168.2.1

ens33:

addresses:

- 172.16.1.230/16

Disable the Uncomplicated Firewall (UFW)

# systemctl disable ufw

Disable swap partition in fstab.

# cat /etc/fstab | grep swap
#/swap.img none swap sw 0 0

Reboot to apply changes

# reboot

3. kub02.darole.org

Set the hostname

# hostnamectl set-hostname kub02.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces using Netplan

# cat /etc/netplan/00-installer-config.yaml

network:

version: 2

ethernets:

ens32:

addresses:

- 192.168.2.231/24

gateway4: 192.168.2.1

nameservers:

addresses:

- 192.168.2.1

ens33:

addresses:

- 172.16.1.231/16

Disable the Uncomplicated Firewall (UFW)

# systemctl disable ufw

Disable swap partition in fstab.

# cat /etc/fstab | grep swap
#/swap.img none swap sw 0 0

Reboot to apply changes

# reboot

4. tomd01.darole.org

Ubuntu VMs are known for their ease of use with the Ubuntu repository. Here's how to configure hostname and network:

Set the hostname

# hostnamectl set-hostname tomd01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces using Netplan

# sed -i 's/172.16.1.227/172.16.1.250/g' /etc/netplan/50-cloud-init.yaml

# sed -i 's/192.168.2.227/192.168.2.250/g' /etc/netplan/50-cloud-init.yaml

# cat /etc/netplan/50-cloud-init.yaml

network:

version: 2

ethernets:

ens192:

addresses:

- 192.168.2.250/24

gateway4: 192.168.2.1

nameservers:

addresses:

- 192.168.2.1

ens160:

addresses:

- 172.16.1.250/16

Disable the Uncomplicated Firewall (UFW)

# systemctl disable ufw

Reboot to apply changes

# reboot

5. tomp01.darole.org

Ubuntu VMs are known for their ease of use with the Ubuntu repository. Here's how to configure hostname and network:

Set the hostname

# hostnamectl set-hostname tomp01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces using Netplan

# sed -i 's/172.16.1.227/172.16.1.251/g' /etc/netplan/50-cloud-init.yaml

# sed -i 's/192.168.2.227/192.168.2.251/g' /etc/netplan/50-cloud-init.yaml

# cat /etc/netplan/50-cloud-init.yaml

network:

version: 2

ethernets:

ens192:

addresses:

- 192.168.2.251/24

gateway4: 192.168.2.1

nameservers:

addresses:

- 192.168.2.1

ens160:

addresses:

- 172.16.1.251/16

Disable the Uncomplicated Firewall (UFW)

# systemctl disable ufw

Reboot to apply changes

# reboot

Go to topics

5. gra01.darole.org

Ubuntu VMs are known for their ease of use with the Ubuntu repository. Here's how to configure hostname and network:

Set the hostname

# hostnamectl set-hostname gra01.darole.org

# scp vallabh@172.16.1.223:/etc/hosts /etc/

Configure the network interfaces using Netplan

# sed -i 's/172.16.1.227/172.16.1.241/g' /etc/netplan/50-cloud-init.yaml

# sed -i 's/192.168.2.227/192.168.2.241/g' /etc/netplan/50-cloud-init.yaml

# cat /etc/netplan/50-cloud-init.yaml

network:

version: 2

ethernets:

ens192:

addresses:

- 192.168.2.241/24

gateway4: 192.168.2.1

nameservers:

addresses:

- 192.168.2.1

ens160:

addresses:

- 172.16.1.241/16

Disable the Uncomplicated Firewall (UFW)

# systemctl disable ufw

Reboot to apply changes

# reboot

Task 10. Puppet server configuration on pup01.

In this report, we document the steps taken to configure the Puppet server (pup01) for centralized management and automation of IT infrastructure tasks within the environment.

1. Installation and Configuration of Puppet Server:

- Installed the Puppet Server repository.

- Installed the Puppet Server package.

- Configured Puppet Server Java arguments.

# dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm

# dnf -y install https://yum.puppetlabs.com/puppet-release-el-8.noarch.rpm

# dnf install -y puppetserver

# vi /etc/sysconfig/puppetserver

JAVA_ARGS="-Xms512m -Xmx512m Djruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger"

- Configured Puppet Master settings.

# vi /etc/puppetlabs/puppet/puppet.conf

[master]

dns_alt_names = pup01.darole.org

[main]

certname = pup01.darole.org

server = pup01.darole.org

environment = production

runinterval = 1h

- Set up Puppet Certificate Authority (CA).

# /opt/puppetlabs/bin/puppetserver ca setup

- Started and enabled Puppet Server.

# systemctl start puppetserver

# systemctl enable puppetserver

2. Configuration of Puppet Manifests:

- Installed Git for version control.

- Created a directory for Git and navigated to it.

- Cloned the Puppet Git repository.

- Copied Puppet module files to the production environment.

- Copied Puppet manifest files to the production environment.

# yum install git -y

# mkdir /git-data ; cd /git-data

# git clone https://github.com/vdarole/puppet.git

# cp -rf /git-data/puppet/modules/* /etc/puppetlabs/code/environments/production/modules/

# cp -rf /git-data/puppet/manifests/* /etc/puppetlabs/code/environments/production/manifests/

3. Application of Puppet Manifests:

- were created for various tasks to ensure consistent and automated configuration across servers.

- These manifests include tasks such as banner creation, Bash history setup, user management, package installation, and NTP configuration.

- Servers ans01, zap01, dock01, lamp01, web01, and db01 were configured to connect to the Puppet server (pup01) and apply the relevant manifests.

4. Copied the Puppet agent installation script to all servers.

# scp /git-data/ansible/puppet-agent-install-rhel8.sh zap01:/root

# scp /git-data/ansible/puppet-agent-install-rhel8.sh jen01:/root

# scp /git-data/ansible/puppet-agent-install-rhel8.sh lamp01:/root

# scp /git-data/ansible/puppet-agent-install-rhel8.sh web01:/root

# scp /git-data/ansible/puppet-agent-install-rhel8.sh db01:/root

scp /git-data/ansible/puppet-agent-install-rhel8.sh son01:/root

# scp /git-data/ansible/puppet-agent-install-ubuntu20.sh vallabh@dock01:/tmp

# scp /git-data/ansible/puppet-agent-install-ubuntu20.sh vallabh@kub01:/tmp

# scp /git-data/ansible/puppet-agent-install-ubuntu20.sh vallabh@kub02:/tmp

# scp /git-data/ansible/puppet-agent-install-ubuntu20.sh vallabh@tomd01:/tmp

# scp /git-data/ansible/puppet-agent-install-ubuntu20.sh vallabh@tomp01:/tmp

# scp /git-data/ansible/puppet-agent-install-ubuntu20.sh vallabh@gra01:/tmp

- Executed the agent installation script on all servers.

# sh puppet-agent-install-ubuntu18.sh ( on ubuntu)

# sh puppet-agent-install-rhel8.sh (on redhat)

# sh puppet-agent-install-rhel8.sh (on rocky)

5. Logged in to the Puppet server to check the agent status and accepted it.

# puppetserver ca list --all

# puppetserver ca sign --all

# puppet agent -t

6. Log in to the ans01 server with the "vallabh" user and execute the command: "puppet agent -t." This will implement the Puppet manifest and create the "ansible" user. Then, log in to the ans01 server using the "ansible" user and execute the following commands:

ansible@ans01:~$ ssh-keygen

ansible@ans01:~$ ssh-copy-id pup01

7. After that, log in to the "pup01" server as the root user and copy the "ansible" authorized key to the following location:

# cp /home/ansible/.ssh/authorized_keys /etc/puppetlabs/code/environments/production/modules/ansfile/files/authorized_keys

Task 10. Implement LAMP Application on development (lamp01) and production (web01 and db01).

In this section, we'll implementing the LAMP (Linux, Apache, MySQL, PHP) application stack on "lamp01," "web01," and "db01" servers using Ansible playbooks. Below are the detailed steps for each server:

1. Implementation of LAMP Application on "lamp01" Server:

During task 6, we had already downloaded the playbook from the Git repository to the Ansible server in the following location:

# apt update

# apt install ansible

# cd /git-data/ansible

Next, move the 'lamp01' folder from '/git-data/ansible' to '/home/ansible'

# mv lamp01 /home/ansible

After moving the folder, change the ownership of the files

# chown -R ansible.ansible /home/ansible/lamp01

Run Ansible playbooks for LAMP application implementation on "lamp01" server

# ansible-playbook webserver-installation.yml -i inventory.txt
# ansible-playbook mariadb-installation.yml -i inventory.txt
# ansible-playbook php-installation.yml -i inventory.txt
# ansible-playbook create-database.yml -e "dbname=jobsearch" -i inventory.txt
# ansible-playbook create-table.yml -i inventory.txt
# ansible-playbook copy-web-pages.yml -i inventory.txt
# ansible-playbook webserver-installation.yml --tags "Restart Webservice" -i inventory.txt
# ansible-playbook data-update.yml -i inventory.txt

2. Implementation of LAMP Application on "web01" and "db01" Servers:

During task 6, we had already downloaded the playbook from the Git repository to the Ansible server in the following location:

# cd /git-data/ansible

Next, move the 'lamp01' folder from '/git-data/ansible' to '/home/ansible'

# mv web-db /home/ansible

After moving the folder, change the ownership of the files

# chown -R ansible.ansible /home/ansible/web-db

Run Ansible playbooks for LAMP application implementation on "web01" and "db01" servers

# ansible-playbook webserver-installation.yml -i inventory.txt
# ansible-playbook mariadb-installation.yml -i inventory.txt
# ansible-playbook php-installation.yml -i inventory.txt
# ansible-playbook create-database.yml -e "dbname=jobsearch" -i inventory.txt
# ansible-playbook create-table.yml -i inventory.txt
# ansible-playbook copy-web-pages.yml -i inventory.txt
# ansible-playbook webserver-installation.yml --tags "Restart Webservice" -i inventory.txt

# ansible-playbook data-update.yml -i inventory.txt

Note: The Ansible playbooks automate the deployment of the LAMP application components (Apache, MySQL, PHP) on the designated servers. This ensures a consistent and reliable setup for the web application across the infrastructure

Go to topics

Task 11. Configuring iSCSI Target and Initiator for Shared Storage:

In our environment, shared storage is a crucial component to ensure high availability and redundancy. This post will guide you through the process of setting up an iSCSI target server on Windows (win01) and configuring iSCSI initiators on Linux nodes (web01 and db01) to enable shared storage.

Setting Up iSCSI Target Server on Windows (win01):

1. Open "Server Manager" on win01.
2. Go to "File and Storage Services" and select "iSCSI."
3. On the right-hand side, click "To create an iSCSI virtual disk, start the New iSCSI Virtual Disk Wizard."

Follow these steps to create the iSCSI virtual disk:

4. Choose the D: drive as the location for the iSCSI virtual disk.
5. Set up the virtual disk size, access paths, and any other necessary configurations.
6. Complete the wizard to create the iSCSI virtual disk.

7. Perform same step for E: drive

Installing and Configuring iSCSI Initiators on Linux (web01 and db01)

On both Linux nodes (web01 and db01), follow these steps to install the iSCSI initiator and attach the iSCSI disk:

1. Install the iSCSI initiator utilities:

# yum install iscsi-initiator-utils -y

2. Discover the iSCSI target on win01:

# iscsiadm -m discovery -t st -p 172.16.1.200

3. Log in to the iSCSI target:

# iscsiadm -m node -T iqn.1991-05.com.microsoft:win01-target01-target -p 172.16.1.200 -l

By following these steps, you've successfully set up an iSCSI target server on your Windows server (win01) and configured iSCSI initiators on your Linux nodes (web01 and db01). This shared storage solution is a fundamental building block for achieving high availability and redundancy in your IT infrastructure.

Go to topics

Task 12. Setup and High Availability Cluster using Pacemaker and Corosync on web01 and db01:

In production IT infrastructures, high availability is crucial to ensure uninterrupted services. This guide takes you through the steps of creating a high availability cluster on web01 and db01 using Pacemaker and Corosync.

1. Update the virtual IP address on both servers to make the website accessible:

# echo "172.16.1.225 jobsearch.darole.org" >> /etc/hosts

2. Enable the High Availability repository (HA) on both nodes.

# subscription-manager repos --enable=rhel-8-for-x86_64-highavailability-rpms

3. Install the PCS package, set the password for the hacluster user, and start the service on both nodes.

# dnf install pcs pacemaker fence-agents-all -y

# passwd hacluster
# systemctl start pcsd

Note : Set password to redhat

4A. On db01, install the httpd package since it's not present by default.

# dnf install -y httpd wget php php-fpm php-mysqlnd php-opcache php-gd php-xml php-mbstring

# systemctl start php-fpm

# systemctl enable php-fpm

5A. Create a partition on the iSCSI disk on web01 and copy the website to it.

# lsblk
# pvcreate /dev/sdb
# vgcreate vgweb /dev/sdb
# lvcreate -L +4G -n lvweb vgweb
# mkfs.xfs /dev/vgweb/lvweb
# mount /dev/vgweb/lvweb /mnt
# cp -R /var/www/html/* /mnt/
# umount /mnt/
# systemctl disable httpd

4B. On web01, install the mariadb-server package since it's not present by default.

# dnf install -y mariadb-server

5A. Create a partition on the iSCSI disk on db01 and copy the website to it.

# systemctl stop mariadb

# lsblk
# pvcreate /dev/sdc
# vgcreate vgdb /dev/sdc
# lvcreate -L +4G -n lvdb vgdb
# mkfs.xfs /dev/vgdb/lvdb
# mount /dev/vgdb/lvdb /mnt

# rsync -avz /var/lib/mysql/ /mnt/

# umount /mnt/

Ensure right ownership

#chown -R mysql:mysql /dev/vgdb/lvdb

Disable mariadb

# systemctl disable mariadb

6. On db01, remount the same iSCSI partition, so that create partition on disk get visible.

#iscsiadm -m node -T iqn.1991-05.com.microsoft:win01-target01-target -p 172.16.1.200 -u

#iscsiadm -m node -T iqn.1991-05.com.microsoft:win01-target01-target -p 172.16.1.200 -l
# lsblk

# mount /dev/vgweb/lv01 /var/www/html/

7. Configure the High Availability Cluster on web01:

# pcs host auth web01 db01 -u hacluster -p redhat

# pcs cluster setup web_cluster --start web01 db01
# pcs cluster start
# pcs cluster status

# pcs property set stonith-enabled=false

# pcs property set no-quorum-policy=ignore

# pcs resource create httpd_fs Filesystem device="/dev/vgweb/lvweb" directory="/var/www/html" fstype="xfs" --group apache
# pcs resource create httpd_vip IPaddr2 ip=172.16.1.225 cidr_netmask=24 --group apache
# pcs resource create httpd_ser apache configfile="/etc/httpd/conf/httpd.conf" statusurl="http://172.16.1.225/" --group apache

#pcs resource create mysql_service systemd:mariadb --group mariadb

# pcs resource create mariadb_vip IPaddr2 ip=172.16.1.226 cidr_netmask=24 op monitor interval=30s --group mariadb

Tell Pacemaker preferred node (location constraints)

# pcs constraint location apache prefers web01=INFINITY

# pcs constraint location mariadb prefers db01=INFINITY

# pcs property set stonith-enabled=false
# pcs cluster status
# pcs status

# pcs resource show

8. On db01, allow root@jobsearch.darole.org to access the database.
# mysql -u root -p
MariaDB > use jobsearch;
MariaDB [jobsearch]> GRANT ALL ON jobsearch.* to 'root'@'172.16.1.226' IDENTIFIED BY 'redhat';

MariaDB [jobsearch]> GRANT ALL ON jobsearch.* to 'root'@'web01.darole.org' IDENTIFIED BY 'redhat';

MariaDB [jobsearch]> GRANT ALL ON jobsearch.* to 'root'@'db01.darole.org' IDENTIFIED BY 'redhat';

Change server name in connection.php file from db01.darole.org to jobsearch.darole.org on web server

# cat /var/www/hmtl/connection.php
#$server_name="db01.darole.org";
$server_name="jobsearch.darole.org";

By following these steps, you've successfully set up a high availability cluster on web01 and db01, ensuring uninterrupted services for your website at http://jobsearch.darole.org/.

Task 13. Setting Up Docker Server and Containers on dock01

Docker is a versatile platform that simplifies the deployment of applications, allowing them to run consistently across different environments. In this post, we will walk you through the installation of Docker on your server, "dock01," and demonstrate how to create Docker containers for hosting various web applications.

Docker Installation

# apt update

# apt install apt-transport-https ca-certificates curl software-properties-common

# curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

# add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable"

# sudo apt update

# apt-cache policy docker-ce

# apt install docker-ce

Download the website template from git hub.

# mkdir /git-data ; cd /git-data
# git clone https://github.com/vdarole/web-temp.git

Docker Cleanup

D. Docker Cleanup:

Once we're done experimenting with our containers, it's essential to perform some cleanup. We can remove all Docker containers and images to keep our system clean.

# docker container rm `docker container ls -a -q` -f
# docker image rm `docker images -q` -f

To automate this process, we've created a simple script for cleanup:

# cat /root/delete-docker.sh

docker container rm `docker container ls -a -q` -f

docker image rm `docker images -q` -f

# crontab -l | grep -v "#"

@reboot /root/delete-docker.sh

root@dock01:~#

Note: There are 2 ways of Volume mounting Container <-> Container and Host <-> Container in the above example we will using Host <-> Container

"-v /git-data/web-temp/Education/:/var/www/html": Mounts a volume from your host system into the container, allowing the container to access the files in that directory.
"-p 172.16.1.216:80:80": Maps port 80 of the host to port 80 of the container.

Go to topics

Task 14. Deploy Kubernetes on kub01 and kub02.

In this blog, we'll walk you through installing Kubernetes on two servers (kub01 and kub02) and deploying an NGINX web server using a service type.

1. Enable iptables Bridged Traffic on all the Nodes

# cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf

overlay

br_netfilter

EOF

# sudo modprobe overlay

# sudo modprobe br_netfilter

# cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf

net.bridge.bridge-nf-call-iptables = 1

net.bridge.bridge-nf-call-ip6tables = 1

net.ipv4.ip_forward = 1

EOF

# sudo sysctl --system

2. Install CRI-O Runtime On All The Nodes

# cat <<EOF | sudo tee /etc/modules-load.d/crio.conf

overlay

br_netfilter

EOF

# cat <<EOF | sudo tee /etc/sysctl.d/99-kubernetes-cri.conf

net.bridge.bridge-nf-call-iptables = 1

net.ipv4.ip_forward = 1

net.bridge.bridge-nf-call-ip6tables = 1

EOF

# sudo modprobe overlay

# sudo modprobe br_netfilter

# cat <<EOF | sudo tee /etc/sysctl.d/99-kubernetes-cri.conf

net.bridge.bridge-nf-call-iptables = 1

net.ipv4.ip_forward = 1

net.bridge.bridge-nf-call-ip6tables = 1

EOF

# sudo sysctl --system

# export OS="xUbuntu_20.04"

# export VERSION="1.28"

# cat <<EOF | sudo tee /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list

deb https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/ /

EOF

# cat <<EOF | sudo tee /etc/apt/sources.list.d/devel:kubic:libcontainers:stable:cri-o:$VERSION.list

deb http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/$VERSION/$OS/ /

EOF

# curl -L https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable:cri-o:$VERSION/$OS/Release.key | sudo apt-key --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg add -

# curl -L https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/$OS/Release.key | sudo apt-key --keyring /etc/apt/trusted.gpg.d/libcontainers.gpg add -

# sudo apt-get update

# sudo apt-get install cri-o cri-o-runc cri-tools -y

# sudo systemctl daemon-reload

# sudo systemctl enable crio --now

3. Install Kubeadm & Kubelet & Kubectl on all Nodes

# sudo mkdir -m 755 /etc/apt/keyrings

# sudo apt-get update

# sudo apt-get install -y apt-transport-https ca-certificates curl gpg

# sudo curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.28/deb/Release.key | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg

# echo 'deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.28/deb/ /' | sudo tee /etc/apt/sources.list.d/kubernetes.list

# sudo apt-get update -y

# sudo apt-get install -y kubelet kubeadm kubectl

# sudo apt-mark hold kubelet kubeadm kubectl

# sudo apt-get install -y jq

local_ip="$(ip --json a s | jq -r '.[] | if .ifname == "ens33" then .addr_info[] | if .family == "inet" then .local else empty end else empty end')"

# cat > /etc/default/kubelet << EOF

KUBELET_EXTRA_ARGS=--node-ip=$local_ip

EOF

4. Initialize Kubeadm On Master Node To Setup Control Plane

# export IPADDR="172.16.1.230"

# export NODENAME=$(hostname -s)

# export POD_CIDR="10.1.0.0/16"

# sudo kubeadm init --apiserver-advertise-address=$IPADDR --apiserver-cert-extra-sans=$IPADDR --pod-network-cidr=$POD_CIDR --node-name $NODENAME --ignore-preflight-errors Swap

5. Test cluster access

# mkdir -p $HOME/.kube

# sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config

# sudo chown $(id -u):$(id -g) $HOME/.kube/config

# kubectl get po -n kube-system

# kubectl cluster-info

6. Install Calico Network Plugin for Pod Networking

# kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.25.1/manifests/calico.yaml

# kubeadm token create --print-join-command

# kubectl get nodes

Example output,

root@master-node:/home/vagrant# kubectl get nodes

NAME STATUS ROLES AGE VERSION

master-node Ready control-plane 14m v1.27.2

worker-node01 Ready <none> 2m13s v1.27.2

Go to topics

Task 15. Configuring Postfix, Dovecot, and SquirrelMail on pup01 Server:

Configuring a mail server involves setting up Postfix for sending and receiving emails, Dovecot for email retrieval (IMAP and POP3), and SquirrelMail as a webmail interface. Here's a step-by-step guide for setting up these components on the "pup01" server:

A. Update MX Record in Win01 DNS Server:

Update the MX record in your Windows Server 2019 DNS configuration to point to the IP address of your "pup01" server. This step ensures that your server is configured to receive emails.

B. Postfix Configuration:

Edit the Postfix main configuration file:

# dnf install postfix
# vi /etc/postfix/main.cf

Modify the following settings:

myhostname = pup01.darole.org ## Add Line
mydomain = darole.org ## Add Line
myorigin = $mydomain ## Uncommit

inet_interfaces = all ## Uncommit

# inet_interfaces = localhost ## commit

# mydestination = $myhostname, localhost.$mydomain, localhost ## commit
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain  ## Uncommit
mynetworks = 172.16.0.0/16, 127.0.0.0/8   ## Uncommit   and update IP
home_mailbox = Maildir/   ## Uncommit

Restart Postfix and enable it to start on boot:

# systemctl restart postfix
# systemctl enable postfix

C. Dovecot Configuration:

Install Dovecot and configure protocols, mailbox location, and authentication mechanisms:

Install Dovecot Package
# yum install -y dovecot

To Configure Dovecot we need to edit multiple configuration files.

Edit file /etc/dovecot/dovecot.conf file
# vi /etc/dovecot/dovecot.conf
protocols = imap pop3 lmtp ## uncomment ##

Edit file /etc/dovecot/conf.d/10-mail.conf file
# vi /etc/dovecot/conf.d/10-mail.conf
mail_location = maildir:~/Maildir ## uncomment ##

Edit /etc/dovecot/conf.d/10-auth.conf
# vi /etc/dovecot/conf.d/10-auth.conf
disable_plaintext_auth = yes ## uncomment ##
auth_mechanisms = plain login ## Add the word: "login" ##

Edit file /etc/dovecot/conf.d/10-master.conf,

# vi /etc/dovecot/conf.d/10-master.conf
unix_listener auth-userdb {
#mode = 0600
user = postfix ## Line 102 - Uncomment and add "postfix"
group = postfix ## Line 103 - Uncomment and add "postfix"

}

Start and enable Dovecot service:

# systemctl start dovecot
# systemctl enable dovecot

D. SquirrelMail Installation and Configuration:

Install SquirrelMail from the Remi repository:

# wget https://www.squirrelmail.org/countdl.php?fileurl=http%3A%2F%2Fprdownloads.sourceforge.net%2Fsquirrelmail%2Fsquirrelmail-webmail-1.4.22.tar.gz

# gunzip countdl.php\?fileurl\=http\:%2F%2Fprdownloads.sourceforge.net%2Fsquirrelmail%2Fsquirrelmail-webmail-1.4.22.tar.gz

# mv countdl.php\?fileurl\=http\:%2F%2Fprdownloads.sourceforge.net%2Fsquirrelmail%2Fsquirrelmail-webmail-1.4.22.tar squirrelmail-webmail-1.4.22.tar

# tar -xvf squirrelmail-webmail-1.4.22.tar

# dnf install -y httpd php php-cli php-common

# mv squirrelmail-webmail-1.4.22 /var/www/html/webmail

# cd /var/www/html/webmail/config

# mkdir /var/www/html/webmail/attach

# chown apache:apache -R /var/www/html/

Navigate to SquirrelMail configuration directory and run configuration script:

# cd /var/www/html/webmail/config/
# ./conf.pl

Create the below file and folder copy the data

mkdir /var/local/squirrelmail/

mkdir /var/local/squirrelmail/attach

cp -r /var/www/html/webmail/data/ /var/local/squirrelmail/

chown -R apache.apache /var/local/squirrelmail/

Add squirrelmail configuration is apache config file:
# vi /etc/httpd/conf/httpd.conf
Alias /webmail /var/www/html/webmail
<Directory "/var/www/html/webmail">
Options Indexes FollowSymLinks
RewriteEngine On
AllowOverride All
DirectoryIndex index.php
Order allow,deny
Allow from all
</Directory>

Restart and enable Apache service.
# systemctl restart httpd
# systemctl enable httpd

Open Web Browser and type the below address

http://pup01.darole.org/webmail/src/login.php

Go to topics

Task 16. Zabbix monitoring deployment on zap01 with client auto-discovery.

Zabbix is a popular open-source monitoring solution used to track various metrics and performance data of IT infrastructure components. Below are the steps taken to deploy Zabbix monitoring using Ansible on the "zap01" server.

Running Ansible Playbooks for Zabbix Monitoring Deployment on "zap01" Server:

During task 6, we had already downloaded the playbook from the Git repository to the Ansible server in the following location:

# cd /git-data/ansible

Next, move the 'lamp01' folder from '/git-data/ansible' to '/home/ansible'

# mv zabbix-5 /home/ansible

After moving the folder, change the ownership of the files

# chown -R ansible.ansible /home/ansible/zabbix-5

Execute Ansible playbooks for Zabbix monitoring deployment on "zap01" server

# ansible-playbook zabbix-installation.yml
# ansible-playbook mariadb-installation.yml
# ansible-playbook create-db-table.yml
# ansible-playbook zabbix-service.yml

Zabbix Monitoring Implementation Process:

The deployment and configuration of Zabbix monitoring involve two processes: installation and configuration on the server side and website. We had complete server side installation now we will proceed with website configuration

1. Welcome screen

2. Will check the requisites.

3. Configure DB connection

Note: Password is redhat

4. Configure Server details.

Note: Name : zap01.darole.org

5. Pre-installation Summary

6. Installation completed.

7. Login screen

Username: Admin

Password: zabbix

8. Let unable Auto Registration of Linux agent

Goto Configuration > Action > Auto Registration > create action.

Action name Linux Server and Host metadata contains LinuxServers.

In Operations add host, add host group and Linux to templates

9. Create two playbooks for installation zabbix agent on Centos, Redhat and ubuntu

$ ansible-playbook zabbix-rhel8-agent.yml

$ ansible-playbook zabbix-ubuntu20-agent.yml

10. Go to console and check for all hosts are visible.

Note: Zabbix is a comprehensive monitoring solution, and the provided Ansible playbooks automate the deployment and initial configuration of Zabbix components. The web-side implementation is essential to configure monitoring items, triggers, and other settings for effective monitoring of your infrastructure. The provided blog link and GitHub repository offer further guidance on the implementation process.

Monitor VMware Esxi hosts using Zabbix 5

1. Login to zap01 and perform the below changes.

# vi /etc/zabbix/zabbix_server.conf | grep -i StartVMwareCollectors

### Option: StartVMwareCollectors

StartVMwareCollectors=5

# systemctl restart zabbix-server

2. Manually add EXSi host details in zabbix portal.

Monitor Docker containers using Zabbix 5

1. Check the docker containers.

root@dock01:~# docker ps

2. Give the permission to zabbix agent to monitor docker.

root@dock01:~# usermod -aG docker zabbix

3. Restart Zabbix Agent and check status.

root@dock01:~# systemctl restart zabbix-agent2

root@dock01:~# systemctl status zabbix-agent2

4. To check the connectivity from zabbix server to docker client use below command.

[root@zap01 ~]# zabbix_get -s dock01 -k docker.info

Create "zap-admin" User for Zabbix Alerts:

Create a user named "zap-admin" to receive alerts from the Zabbix monitoring system.

6. To test the monitoring we will reboot non production server and check on dashboard and on webmail.

Alerts on Dashboard

Email generated for host down.

Task 22 Installing Apache Tomcat 10 on tomd01 and tomp01

Apache Tomcat is a widely used Java servlet container that provides a robust environment for running Java applications. Here's a simple guide to installing Apache Tomcat 10 on Ubuntu 20.04:

Step 1: Create a Tomcat User

# useradd -m -d /opt/tomcat -U -s /bin/false tomcat

Step 2: Update System and Install Java Development Kit (JDK)

# apt update

# apt install default-jdk

# java -version

Step 3: Download and Extract Apache Tomcat

# cd /tmp

# wget https://archive.apache.org/dist/tomcat/tomcat-10/v10.0.11/bin/apache-tomcat-10.0.11.tar.gz

# tar xzvf apache-tomcat-10*tar.gz -C /opt/tomcat --strip-components=1

Step 4: Set Permissions

# chown -R tomcat:tomcat /opt/tomcat/

# chmod -R u+x /opt/tomcat/bin

Step 5: Configure Tomcat Users

# vi /opt/tomcat/conf/tomcat-users.xml

Add the following lines before the closing `</tomcat-users>` tag:

<role rolename="manager-gui" />

<user username="manager" password="redhat" roles="manager-gui" />

<role rolename="admin-gui" />

<user username="admin" password="redhat" roles="manager-gui,admin-gui" />

Save and close the file.

Step 6: Remove IP Restrictions, by committing the below lines

# vi /opt/tomcat/webapps/manager/META-INF/context.xml

<!-- <Valve className="org.apache.catalina.valves.RemoteAddrValve"

allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1" /> -->

# vi /opt/tomcat/webapps/host-manager/META-INF/context.xml

<!-- <Valve className="org.apache.catalina.valves.RemoteAddrValve"

allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1" /> -->

Comment out the Valve definition for both Manager and Host Manager.

Step 7: Configure Tomcat Service and Add the following content.

# vi /etc/systemd/system/tomcat.service

[Unit]

Description=Tomcat

After=network.target

[Service]

Type=forking

User=tomcat

Group=tomcat

Environment="JAVA_HOME=/usr/lib/jvm/java-1.21.0-openjdk-amd64"

Environment="JAVA_OPTS=-Djava.security.egd=file:///dev/urandom"

Environment="CATALINA_BASE=/opt/tomcat"

Environment="CATALINA_HOME=/opt/tomcat"

Environment="CATALINA_PID=/opt/tomcat/temp/tomcat.pid"

Environment="CATALINA_OPTS=-Xms512M -Xmx1024M -server -XX:+UseParallelGC"

ExecStart=/opt/tomcat/bin/startup.sh

ExecStop=/opt/tomcat/bin/shutdown.sh

RestartSec=10

Restart=always

[Install]

WantedBy=multi-user.target

Save and close the file.

Step 8: Reload systemd, Start and Enable Tomcat Service

# systemctl daemon-reload

# systemctl start tomcat

# systemctl enable tomcat

That's it! Apache Tomcat 10 is now installed and configured on your Ubuntu 20.04 server. You can access the Tomcat server by navigating to `http://tomd01:8080` in your web browser.

Follow the same steps and install on tomp01

Deploying a Simple Tomcat Web Application with Maven

In this blog, we will walk through the steps to deploy a simple Tomcat web application using Git and Maven.

Step 1: Create and Navigate to the Git Directory

# mkdir /git ; cd /git

Step 2: Clone the Repository

# git clone https://github.com/vdarole/tomcat-war.git

Step 3: Update the Package List

# apt update

Step 4: Install Maven

# apt install maven

Step 5: Verify Maven Installation

# mvn -version

Step 6: Compile the Project

# cd tomcat-war ; mvn compile

Step 7: Run Tests

# mvn test

Step 8: Package the application into a WAR file

# mvn package

Step 9: Deploy the WAR File to Tomcat

# cp /git/tomcat-war/target/SimpleTomcatWebApp.war /opt/tomcat/webapps/

Step 10: Login to win01 and open the below URL

http://tomp01.darole.org:8080/SimpleTomcatWebApp/

Go to topics

Installing SonarQube on son01

Java 17 install and verification

# dnf install -y java-17-openjdk-devel
# java -version

PostgreSQL install, initialize and basic DB creation

# dnf install -y postgresql-server postgresql-contrib
# postgresql-setup --initdb --unit postgresql
# systemctl enable --now postgresql

Create DB user and DB (replace password with a secure one)

# cd /tmp

# sudo -u postgres psql -c "CREATE USER sonar WITH ENCRYPTED PASSWORD 'redhat';"
# sudo -u postgres psql -c "CREATE DATABASE sonarqube OWNER sonar ENCODING 'UTF8' LC_COLLATE='en_US.utf8' LC_CTYPE='en_US.utf8' TEMPLATE template0;"
# sudo -u postgres psql -c "GRANT ALL PRIVILEGES ON DATABASE sonarqube TO sonar;"

: ensure password auth for SonarQube
find active file

# sudo -u postgres psql -t -c "SHOW hba_file;"

Edit /var/lib/pgsql/data/pg_hba.conf and add and # ident:

# vi /var/lib/pgsql/data/pg_hba.conf

local all sonar md5

host all sonar 127.0.0.1/32 md5

host all sonar ::1/128 md5

Reload postgres after edit

# sudo systemctl reload postgresql

Reset sonar password to match sonar.properties

# sudo -u postgres psql -c "ALTER USER sonar WITH ENCRYPTED PASSWORD 'redhat';"

Download and install SonarQube to /opt

# cd /opt
# dnf install -y unzip curl
# curl -L -O https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-9.9.0.65466.zip
# unzip sonarqube-9.9.0.65466.zip
# mv sonarqube-9.9.0.65466 sonarqube

Create sonar user, ownership and permissions

# groupadd sonar
# useradd -r -s /sbin/nologin -g sonar sonar
# chown -R sonar:sonar /opt/sonarqube
# chmod -R 755 /opt/sonarqube

Add the below lines to set JDBC, web host for sonar.properties

# vi /opt/sonarqube/conf/sonar.properties
sonar.jdbc.username=sonar
sonar.jdbc.password=redhat
sonar.jdbc.url=jdbc:postgresql://127.0.0.1:5432/sonarqube
sonar.web.host=0.0.0.0
sonar.web.port=9000

Make systemd use Java 17 for SonarQube (drop-in)

# mkdir -p /etc/systemd/system/sonarqube.service.d

# cat > /etc/systemd/system/sonarqube.service.d/java.conf <<'EOF'
[Service]
Environment="JAVA_HOME=/usr/lib/jvm/java-17-openjdk"
Environment="PATH=/usr/lib/jvm/java-17-openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin"
EOF

# systemctl daemon-reload

Create a systemd unit for SonarQube

# vi /etc/systemd/system/sonarqube.service

[Unit]
Description=SonarQube service
After=syslog.target network.target postgresql.service
[Service]
Type=forking
ExecStart=/opt/sonarqube/bin/linux-x86-64/sonar.sh start
ExecStop=/opt/sonarqube/bin/linux-x86-64/sonar.sh stop
User=sonar
Group=sonar
LimitNOFILE=65536
LimitNPROC=4096
TimeoutStartSec=300
Restart=on-failure
[Install]
WantedBy=multi-user.target

Elasticsearch kernel tuning

# sysctl -w vm.max_map_count=262144

#cat > /etc/sysctl.d/99-sonarqube.conf <<'EOF'
vm.max_map_count=262144
EOF

# sysctl --system

Start and check SonarQube

# systemctl enable --now sonarqube

# journalctl -u sonarqube -f

or run interactive for debugging

#sudo -u sonar /opt/sonarqube/bin/linux-x86-64/sonar.sh console

test HTTP

# curl -v http://127.0.0.1:9000/

http://son01.darole.org:9000/

User name: admin

Password: admin

Change the username and password after first login.

Below is dash board of maven

Generate Token and keep safe

Token: sqa_361fedc9dc911e16f5cc6dd1f4a3b3145318c97f

Now integration of Maven with sonarQube

Go to project file and update the plugin in pom.xml in plugins sessions.

root@tomd01:/git/tomcat-war# cat pom.xml

<plugin>

<groupId>org.sonarsource.scanner.maven</groupId>
<artifactId>sonar-maven-plugin</artifactId>
<version>3.9.1.2184</version>
</plugin>

</plugins>
</build>
</project>

Maven command to run a Sonar analysis using a token

root@tomd01:/git/tomcat-war# mvn clean verify sonar:sonar \
-Dsonar.host.url=http://son01.darole.org:9000 \
-Dsonar.login=sqa_361fedc9dc911e16f5cc6dd1f4a3b3145318c97f

root@tomd01:/git/tomcat-war# mvn compile test package

# cp /git/tomcat-war/target/.war /opt/tomcat/webapps/

http://tomd01.darole.org:8080/SimpleTomcatWebApp/

Task 23 . Jenkin server configuration on jen01.

In this section, we will walk through the configuration steps taken to set up the Jenkin server (jen01) and perform various automation tasks within the environment.

Updating Jenkins Server:

To ensure compatibility with the latest Jenkins modules, we updated the "jen01" virtual machine Ubuntu 24. Below are the steps followed for each upgrade:

VM Specifications

Hostname: Rocky
CPU: 1
Memory: 1 GB
Disk: 16 GB
Internal IP: 172.16.1.252
External IP: 172.16.1.252
User: root
Password: redhat

Installation and Setup Steps

1. Install Java, wget, and rsyslog:

# dnf install java-24-openjdk-devel wget rsyslog

2. Start rsyslog service:

# systemctl start rsyslog

3. Add Jenkins repository:

# wget -O /etc/yum.repos.d/jenkins.repo https://pkg.jenkins.io/redhat/jenkins.repo

4. Import Jenkins GPG key:

# rpm --import https://pkg.jenkins.io/redhat/jenkins.io-2023.key

5. Install Jenkins:

# dnf install jenkins

6. Start Jenkins service:

# systemctl start jenkins

7. Enable Jenkins to start on boot:

# systemctl enable jenkins

8. Check Jenkins service status:

# systemctl status jenkins

9. Access Jenkins

Open a browser and navigate to http://jen01.darole.org:8080

Retrieve the Initial Admin Password

To unlock Jenkins, you need to retrieve the initial admin password from the Jenkins server.

# cat /var/lib/jenkins/secrets/initialAdminPassword

Copy the password displayed in the terminal.

10. Install Suggested Plugins

On the "Customize Jenkins" page, select "Install suggested plugins."

Jenkins will automatically install the recommended plugins. This may take a few minutes.

11. Create the First User

Once the plugins are installed, you will be prompted to create the first Jenkins user.

Fill in the following fields:

Username: admin
Password: redhat
Full name: administrator
Email: ansible@pup01.darole.org

Click "Save and Finish."

12. Configure Jenkins URL

On the "Instance Configuration" page, set the Jenkins URL to http://jen01.darole.org:8080/.

Click "Save and Finish."

13. Jenkins is Ready

You will see a confirmation page indicating that "Jenkins is ready!"

Click "Start using Jenkins" to proceed to the Jenkins dashboard.

14. Jenkins Dashboard

You will now be directed to the Jenkins dashboard, where you can start creating jobs, managing configurations, and utilizing all the features Jenkins offers.

Jenkins Agent Installation and Configuration.

Click on Manage Jenkins.

Scroll Down to Security.

Under Security settings, go to Agents and Select TCP port for inbound agents as "Random", then Save and exit.

Go to Dashboard then click on Manage Jenkins

Click on Nodes

Click on new Node

Enter the node name as dock01 (since we are implementing it on the dock01 node). Select Permanent Agent and click on Create.

Set the Remote root directory to /root/jenkins.(Ensure this directory is created on the dock01 node as well.) Click Save and Close.

Click on dock01 to configure the agent.

After clicking on dock01, you will see the agent connection command.

Copy the command and execute it on the dock01 server. Run the following commands sequentially on dock01:

root@dock01:~# apt update

root@dock01:~# apt install default-jre

root@dock01:~# apt install openjdk-21-jre-headless

root@dock01:~# curl -sO http://jen01.darole.org:8080/jnlpJars/agent.jar

root@dock01:~# java -jar agent.jar -url http://jen01.darole.org:8080/ -secret 8331411ab4e1600c2e15067f0cb5ad345713d78436f6c40d71cb5f7c9290cca7 -name dock01 -workDir "/root/jenkins"&

Once the commands are executed, the agent installation will be completed. You should see the dock01 node details in Jenkins.

Building and Deploying Software Projects in Jenkins

1. Deploying the "Travel-Site" Project

Step 1: Navigate to the Jenkins Dashboard

Click on New Item.

Step 2: Configure Project

Name the project travel-site.
Select Freestyle Project and click OK.

Step 3: Configure Source Code Management

On the project configuration page:

Set GitHub project with the URL: https://github.com/vdarole/jenkin.git.
Under Source Code Management, choose Git and provide the repository URL: https://github.com/vdarole/jenkin.git.
Specify the branch to build as */main.

Step 4: Restrict Project to Run on Specific Nodes

Check Restrict where this project can be run.

Enter dock01 in the field to ensure this project runs on the dock01 node.

Step 5: Add Build Steps

Under Build, select Execute Shell.

Paste the following script:

docker build -t nginx_ubuntu .
docker container run --name travel -dit -v /git-data/web-temp/Travel/:/var/www/html -p 172.16.1.218:80:80 nginx_ubuntu
docker exec -d travel /usr/bin/systemctl start nginx

Save and exit.

Step 6: Save and Trigger Build

Click Save and then Build Now.

Step 7: Monitor Build Output

Once the build starts, click on the Build Number under Build History.

Navigate to Console Output to monitor the build progress.

Step 8: Verify Deployment

root@dock01:~# docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

430aff3b126e nginx_ubuntu "/bin/bash" About a minute ago Up About a minute 172.16.1.218:80->80/tcp farm

root@dock01:~#

Open the browser and visit: http://travel.darole.org/.

2. Deploying the "Carvilla" Project

Step 1: Create a New Project

Navigate to the Jenkins Dashboard.

Click on New Item, name the project carvilla, and select Freestyle Project. Click OK.

Name the Project as carvilla, Select Freestyle Project option. then click on ok

Step 2: Configure Project

Configure it similarly to the travel-site project:

GitHub project URL: https://github.com/vdarole/jenkin.git.
Git Repository URL: https://github.com/vdarole/jenkin.git.
Branch to build: */main.

Step 3: Restrict Project to Run on Specific Nodes

Under General, check Restrict where this project can be run and set the node as dock01.

Branches to build is */main

Step 4: Add Build Steps

Under Build, select Execute Shell and paste the following script:

docker build -t nginx_ubuntu .
docker container run --name carvilla -dit -v /git-data/web-temp/carvilla/:/var/www/html -p 172.16.1.220:80:80 nginx_ubuntu
docker exec -d carvilla /usr/bin/systemctl start nginx

Save and exit.

Step 5: Save and Trigger Build

Click Save and then Build Now.

Step 6: Monitor Build Output

Access the Console Output for the build to ensure it runs successfully.

Step 7: Verify Deployment

root@dock01:~# docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

58237a873ade nginx_ubuntu "/bin/bash" About a minute ago Up About a minu te 172.16.1.220:80->80/tcp carvilla

b501cda42533 nginx_ubuntu "/bin/bash" 2 hours ago Up 2 hours 172.16.1.218:80->80/tcp travel

root@dock01:~#

Open the browser and visit: http://carvilla.darole.org/.

📊 What is Grafana?

Grafana is an open-source data visualization platform.
It connects to Prometheus (and many other sources) to visualize data in interactive dashboards and graphs.

⚙️ Step 1: Update Ubuntu 20.04 Server

# apt update &&  apt upgrade -y

🧠 Step 2: Install Prometheus on Ubuntu 20.04

1️⃣ Create Prometheus user and directories

# useradd --no-create-home --shell /bin/false prometheus
# mkdir /etc/prometheus /var/lib/prometheus

2️⃣ Download Prometheus

# cd /tmp
# wget https://github.com/prometheus/prometheus/releases/download/v2.53.0/prometheus-2.53.0.linux-amd64.tar.gz
# tar xvf prometheus-2.53.0.linux-amd64.tar.gz
# cd prometheus-2.53.0.linux-amd64

3️⃣ Move binaries and set permissions

#  mv prometheus /usr/local/bin/
#  mv promtool /usr/local/bin/
#  mv consoles /etc/prometheus/
# mv console_libraries /etc/prometheus/
# mv prometheus.yml /etc/prometheus/
# chown -R prometheus:prometheus /etc/prometheus /var/lib/prometheus
# chown prometheus:prometheus /usr/local/bin/prometheus /usr/local/bin/promtool

🧾 Step 3: Create Prometheus Systemd Service

# tee /etc/systemd/system/prometheus.service > /dev/null <<EOF
[Unit]
Description=Prometheus Monitoring
Wants=network-online.target
After=network-online.target

[Service]
User=prometheus
Group=prometheus
Type=simple
ExecStart=/usr/local/bin/prometheus \
    --config.file=/etc/prometheus/prometheus.yml \
    --storage.tsdb.path=/var/lib/prometheus/ \
    --web.console.templates=/etc/prometheus/consoles \
    --web.console.libraries=/etc/prometheus/console_libraries

[Install]
WantedBy=multi-user.target
EOF

Then enable and start Prometheus:

# systemctl daemon-reload
# systemctl enable prometheus
# systemctl start prometheus
# systemctl status prometheus

Access it in your browser:
👉 http://gra01.darole.org:9090/

📈 Step 4: Install Grafana on Ubuntu 20.04

1️⃣ Add Grafana APT repository

# apt install -y apt-transport-https software-properties-common curl gpg
# mkdir -p /usr/share/keyrings/
# curl -fsSL https://packages.grafana.com/gpg.key | sudo gpg --dearmor -o /usr/share/keyrings/grafana.gpg
# echo "deb [signed-by=/usr/share/keyrings/grafana.gpg] https://packages.grafana.com/oss/deb stable main" | 
sudo tee /etc/apt/sources.list.d/grafana.list

2️⃣ Install Grafana

# apt update
# apt install grafana -y

3️⃣ Enable and Start Grafana

# systemctl enable grafana-server
# systemctl start grafana-server

Open Grafana in a browser:
👉 http://gra01.darole.org:3000/

(Default credentials: admin / admin)

🔗 Step 5: Connect Grafana to Prometheus

Login to Grafana → http://gra01.darole.org:3000
Go to Connections → Data Sources → Add Data Source
Choose Prometheus
In URL → http://gra01.darole.org:9090
Click Save & Test

🖥️ Step 6: Install Node Exporter on Clients

➤ On Rocky Linux 8 & Ubuntu Clients

Run these commands on each client system (both Rocky 8 and Ubuntu):

Download Node Exporter
# cd /tmp
# wget https://github.com/prometheus/node_exporter/releases/download/v1.8.2/node_exporter-1.8.2.linux-amd64.tar.gz
# tar xvf node_exporter-1.8.2.linux-amd64.tar.gz
# mv node_exporter-1.8.2.linux-amd64/node_exporter /usr/local/bin/

Create a user
# useradd --no-create-home --shell /bin/false node_exporter

Create systemd service
# tee /etc/systemd/system/node_exporter.service > /dev/null <<EOF
[Unit]
Description=Prometheus Node Exporter
After=network.target

[Service]
User=node_exporter
Group=node_exporter
Type=simple
ExecStart=/usr/local/bin/node_exporter

[Install]
WantedBy=multi-user.target
EOF

# systemctl daemon-reload
# systemctl enable node_exporter
# sudo systemctl start node_exporter

Default metrics endpoint →
👉 http://lamp01.darole.org:9100/metrics

🔧 Step 7: Add Clients to Prometheus Server

Edit Prometheus config on your main Ubuntu 20.04 server:

root@gra01:~# vi /etc/prometheus/prometheus.yml

Add client targets at the bottom:

scrape_configs:
  - job_name: "prometheus"
    static_configs:
      - targets: ["localhost:9090"]

  - job_name: "node_exporter"
    static_configs:
      - targets:

          - "lamp01.darole.org:9100"
          - "zap01.darole.org:9100"

Replace the IPs with your Rocky 8 and Ubuntu client IPs.

Then restart Prometheus:

# sudo systemctl restart prometheus

✅ Step 8: Verify Monitoring Setup

Prometheus Targets:
👉 http://gra01.darole.org:9090/targets
Grafana Dashboards:
👉 http://gra01.darole.org:3000

You should now see metrics from all your Ubuntu and Rocky Linux clients visualized beautifully in Grafana.

On-Prem DevOps Infrastructure Project (2026 Edition)

Host System Configuration

Virtual Machines in the Lab

Task 1. Installation and configuration of Windows Server 2019 on VMWare WorkStation 16 pro.

Task 2. Add A and MX records to DNS hosted on win01.

Task 3: ESXi Host Deployment and Configuration on VMware WorkStation.

Task 4. Deploying the vCenter Server Appliance on esxi01.

Task 5. Virtual networking setup on VCenter01.

Task 6. Create ISO store and VM templates.

Task 7. Infrastructure Automation with Terraform

Output

Task 8: Ansible Server Configuration (ans01)

1. Creating and Configuring Ansible Server

Commands

Network Configuration

2. Updating the Server

3. Installing Ansible and Dependencies

4. Using Ansible Playbooks for VM Creation

vars.yml

5. VM Creation Details

6. VM Migration

7. Repository

Installing SonarQube on son01

Jenkins Agent Installation and Configuration.

Building and Deploying Software Projects in Jenkins

📊 What is Grafana?

⚙️ Step 1: Update Ubuntu 20.04 Server

🧠 Step 2: Install Prometheus on Ubuntu 20.04

1️⃣ Create Prometheus user and directories

2️⃣ Download Prometheus

3️⃣ Move binaries and set permissions

🧾 Step 3: Create Prometheus Systemd Service

📈 Step 4: Install Grafana on Ubuntu 20.04

1️⃣ Add Grafana APT repository

2️⃣ Install Grafana

3️⃣ Enable and Start Grafana

🔗 Step 5: Connect Grafana to Prometheus

🖥️ Step 6: Install Node Exporter on Clients

➤ On Rocky Linux 8 & Ubuntu Clients

🔧 Step 7: Add Clients to Prometheus Server

✅ Step 8: Verify Monitoring Setup

No comments:

Post a Comment