Bobcares

Proxmox Ansible Automation | How To?

by | Nov 10, 2022

The article provides a detailed description of Proxmox automation with Ansible. Bobcares, as a part of our Proxmox Support Services, offers solutions to every query that comes our way.

Proxmox Automation With Ansible

proxmox ansible automation

 

Software Installation

1. We can install the community-general collections package via ansible-galaxy using the below code:

ansible-galaxy collection install community.general

2. Then we must install Python v2.7 pip by running the below code:

sudo apt install python-pip

3. We can install python v3 pip (pip3) by running the code:

sudo apt install python3-pip

Here, we use python3 pip on the Ansible host machine and Proxmox Machine.  We use Python2.7 pip on the Proxmox machine only if the Ansible playbook throws errors around “Proxmoxer” not installed on the Proxmox host.

4. Then install Proxmoxer by running the code:

sudo pip3 install proxmoxer # For python3 pip (pip3) # OR sudo pip install proxmoxer # For python2.7 pip

Pre-requisites

  1. Already set SSH and Authentication to the targeted Proxmox server.
  2. Ansible setup using Ansible docs.
  3. Basic Ubuntu 20.04, its container, with 2 Cpu cores, 512 MB Memory, and 16 GB of storage.
  4. Nameserver at 10.100.0.1 on VLAN 50, the Prod.lab domain.
  5. ISO/templates that will reference when setting up the OS are located on a mounted NFS volume called ISOimages_alpha.
  6. Storing Container & VM disks on the Local Proxmox volume and using local for the storage volume. if templates are local to the Machine, use local for the Template volume.
  7. Proxmox server has a ZFS pool, where all the Container & VM disks are located. This has the Volume name mxzfs.

Creating Playbook

We can create the playbook.yml file and begin the setup structure as shown below.

- name: The name of the Playbook
  hosts: 'The host target' # host.example.com
  tasks:
  - name: 'The name of this task'
    proxmox: # community.general.proxmox module reference
    ...
    # All the proxmox.module parameters go here
    ...

Let’s see the playbook with more details. E.g.,

---
- name: Create new LXC container in Proxmox Cygnus Host

hosts: 'cygnus.prod.lan'
tasks:
- name: 'Create Container'
proxmox:
vmid: '300' # Specifying Container ID
api_user: 'root@pam' # Proxmox user
api_password: apiPassword # Password in plaintext !!!
api_host: 'cygnus.prod.lan' # Proxmox hostname
password: containerPassword # Password in plaintext !!!
hostname: 'test.prod.lab' # Container hostname
node: 'cygnus' # Name of Proxmox host
cores: '1'
cpus: '2'
cpuunits: '1000'
ostemplate: 'ISOimages_Alpha:vztmpl/ubuntu-20.04-standard_20.04-1_amd64.tar.gz' # Or use local:vztmpl/... as discussed
storage: 'mxzfs' # Or use 'local' as discussed
disk: '16'
memory: '512'
nameserver: '10.100.0.1'
netif: '{"net0":"name=eth0,ip=dhcp,ip6=dhcp,bridge=vmbr0,tag=50"}'
searchdomain: 'prod.lab'
state: 'present'

Running Playbook

We can run the playbook using the code:

ansible-playbook playbook.yml

[Looking for a solution to another query? We are just a click away.]

Conclusion

In this article, we included the method from our Support team for Proxmox automation with Ansible.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF