Back to articles
DevOps & Systems

Fleet Management and Bulk VPS Configuration Automation with Ansible

Ansible is a popular DevOps configuration management and automation tool that enables centralized control of multiple VPS servers. This guide walks through setting up an Ansible...

DPTCloud Engineering5 min read
Fleet Management and Bulk VPS Configuration Automation with Ansible

Image credit: Wolfgang-1958 · Pixabay Content License

Ansible is a popular DevOps configuration management and automation tool that enables centralized control of multiple VPS servers. This guide walks through setting up an Ansible environment to manage, configure, and deploy applications across multiple VPS instances in a synchronized and automated way. It covers environment setup, inventory configuration, playbook creation, and basic tasks like package installation, application deployment, and status verification.

Introduction to Ansible and Bulk VPS Management

Ansible is an IT automation tool based on SSH, requiring no agent installation on target servers. It uses a declarative model to define the desired system state, enabling efficient management of multiple VPS instances within an organization. With fast deployment and ease of use, Ansible is ideal for businesses managing large VPS clusters, especially in cloud environments like NVMe Cloud VPS for Docker, Nginx & Databases [en/vps](/en/vps).

In modern application development, deploying multiple VPS instances for services such as web servers, databases, or containers requires synchronized management. Ansible allows you to create playbooks that define tasks like package installation, service configuration, or application deployment. Each playbook can be applied across multiple servers simultaneously, ensuring consistency and reducing operational time.

Setting Up the Ansible Environment

To begin, you need an Ansible control node. This can be a dedicated VPS or a local machine. First, install Ansible using the package manager:

sudo apt update
sudo apt install ansible -y

After installation, verify the Ansible version to ensure success:

ansible --version

Ansible uses an inventory file to define target servers. Create the inventory file at /etc/ansible/hosts and add the VPS instances to manage. For example:

[vps_servers]
192.168.1.10 ansible_user=ubuntu
192.168.1.11 ansible_user=ubuntu
192.168.1.12 ansible_user=ubuntu

Ensure the target VPS instances can connect via SSH to the Ansible control node. Use SSH keys for passwordless authentication. Test connectivity with:

ansible all -m ping

Writing Playbooks for VPS Configuration

Ansible playbooks are YAML-defined task collections. Each playbook can perform multiple actions like package installation, directory creation, or service startup. Below is an example playbook to install Nginx on all VPS instances in the inventory:

---
- name: Install and configure Nginx on VPS servers
  hosts: vps_servers
  become: yes
  tasks:
    - name: Update package list
      apt:
        update_cache: yes
    - name: Install Nginx
      apt:
        name: nginx
        state: present
    - name: Start and enable Nginx
      service:
        name: nginx
        state: started
        enabled: yes

Save the playbook as nginx_install.yml and run it using:

ansible-playbook nginx_install.yml

Ansible will execute the tasks on each VPS listed in the inventory. You can extend the playbook to deploy other applications like Node.js, PHP, or databases.

Execution and Verification

After running the playbook, verify the status of each VPS to ensure Nginx is installed and running. Access the IP address of each VPS in a browser or use:

curl http://localhost

If Nginx is active, you'll see the default welcome page. Ansible provides detailed task execution logs, helping you monitor and debug issues.

To maintain consistency, create separate playbooks for different tasks such as firewall configuration, Docker installation, or deploying Node.js/Next.js applications on VPS with Docker and Nginx reverse proxy [en/blog/huong-dan-toan-dien-deploy-ung-dung-nodejsnextjs-tren-vps-voi-docker-va-nginx-reverse-proxy](/en/blog/huong-dan-toan-dien-deploy-ung-dung-nodejsnextjs-tren-vps-voi-docker-va-nginx-reverse-proxy).

Troubleshooting and Tips

  • SSH connection failed: Check SSH keys, firewall rules, and VPS IP addresses. Ensure the Ansible control node has access.
  • Playbook not executing: Verify YAML syntax, command errors, or sudo permissions on target machines.
  • Dry run: Use ansible-playbook --check to preview actions before execution.

Ansible supports advanced features like variables, conditions, and loops. Explore the official Ansible documentation to expand your automation capabilities.

References

  • [Comprehensive Guide to Deploying Node.js/Next.js Applications on VPS with Docker and Nginx Reverse Proxy](/en/blog/huong-dan-toan-dien-deploy-ung-dung-nodejsnextjs-tren-vps-voi-docker-va-nginx-reverse-proxy)
  • [Configure VPS High Availability with Keepalived and Floating IP: Comprehensive Guide for Enterprises](/en/blog/cau-hinh-vps-high-availability-voi-keepalived-va-floating-ip-huong-dan-toan-dien-cho-doanh-nghiep)
  • [3-2-1 Strategy for Comprehensive Data Protection on VPS](/en/blog/backup-va-disaster-recovery-cho-vps-chien-luoc-3-2-1-bao-ve-du-lieu-toan-dien)

Related infrastructure & engineering guides: NVMe Cloud VPS for Docker, Nginx & Databases · Comprehensive Digital Transformation for SMEs in 10 Months: Optimizing ERPNext on Docker VPS

DPTCloud Tier III Infrastructure

Recommended NVMe Cloud VPS Plans to Deploy This Setup

Enterprise RAID 10 NVMe SSDs, CMC & FPT District 9 uplinks with Anycast Anti-DDoS and 99.99% SLA.

View 22 VPS Plans
ECO · vn-02

VPS-2E

94.600 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 2 GB
  • SSD: 30 GB NVMe
ECO · vn-02Recommended

VPS-3E

170.500 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 4 GB
  • SSD: 50 GB NVMe
BASIC · vn-01Recommended

VPS-05

457.600 ₫ / mo

10% VAT included

  • CPU: 4 vCPU
  • RAM: 8 GB
  • SSD: 50 GB NVMe

Related Articles

View all
ZaloZalo SupportDiscord0384 753 478