terraform-provider-libvirt VS terraform-provider-proxmox

libvirt-terraform-provider ( based on https://github.com/dmacvicar/terraform-provider-libvirt )

Hi guys!I wanted to allotment with you a tool to provision a fully working OCP 4.x.y cluster in minutes using Ansible for automation, libvirt as virtualization provider and terraform as VMs templating and creation tool. https://github.com/kubealex/libvirt-ocp4-provisioner It will take care of all the infrastructure provisioning and OCP machines provisioning, starting and completing the UPI installation of a cluster. (IPI work in progress ;) ) To give a quick overview, this project will allow you to provision a fully working OCP stable environment, consisting of: * Bastion machine provisioned with: * dnsmasq (with SELinux module, compiled and activated) * dhcp based on dnsmasq * nginx (for ignition files and rhcos pxe-boot) * pxeboot * Loadbalancer machine provisioned with: * haproxy * OCP Bootstrap machine * OCP Master(s) VM(s) * OCP Worker(s) VM(s) From latest release, it also supports installing SNO on a single host! It also takes care of preparing the host machine with needed packages, configuring: * dedicated libvirt network (fully customizable) * dedicated libvirt storage pool (fully customizable) * terraform * libvirt-terraform-provider ( compiled and initialized based‏‏‎‏‏‎‏‏‎‏‏‎­on https://github.com/dmacvicar/terraform-provider-libvirt) PXE is automatic, based on MAC binding to different OCP nodes role, so no need of choosing it from the menus, this means you can just run the playbook, take a beer and have your fully running OCP 4.9.latest stable up and running. It has been tested on Fedora 3x and CentOS 7/8. Playing around with it and contributions to make it work even on different OSes is more than welcome, hope you enjoy it! Alex

I learned and got terraform to work with the KVM/Libvirt provider.

I saw Terraform with the dmacvicar/terraform-provider-libvirt provider, but sadly didn't get really warm with it. When some can explain to me how I can set up new images for every VM I would be very happy also there are more question in the pipeline. Sadly, the “Documentation” is not really that good. Maybe Terraform is also the wrong Application for me. I'm a little lost because I thought Terraform would be the big Solution I want and need, until now, not yet.

It looks like there was an issue dealing with "attaching an existing disk" to a terraform created VM. That's here: https://github.com/dmacvicar/terraform-provider-libvirt/issues/688

Nice. I’m straight KVM as it’s a mirror of work (my Lab) and I’m using the terraform-provider-libvirt provider. 20 minutes to fully build a site. Pretty cool.

libvirt-terraform-provider ( compiled and initialized based on https://github.com/dmacvicar/terraform-provider-libvirt)

Mildly relevant - the Telmate Terraform provider for Proxmox [1], which now stopped working with latest Proxmox version due to seemingly being abandoned, was initially mostly developed by an engineer employed by a company of the same name. They've since rebranded [2].

I've used that provider for a while, and only recently started looking into the specifics. The repo is effectively owned by a company profiting off of incarcerated persons in the US. Pretty wild.

Mostly writing this since I've spent the last few days migrating my Terraform setup to a different, supported provider [3].

[1] https://github.com/Telmate/terraform-provider-proxmox

That's the right answer! Backup all the data that you value, for the rest use the automation tools. Use Ansible to configure the servers and Terraform to provision Proxmox, terraform-provider-proxmox.

Nice guide! It's really a shame that https://github.com/Telmate/terraform-provider-proxmox/issues/600 still hasn't been fixed, otherwise Telmate would be pretty solid. It works pretty well if you don't tinker with multiple applies, though.

I have looked into the Terraform Proxmox provider: https://github.com/Telmate/terraform-provider-proxmox but I don't see anything for creating the disk outside the VM. I'm also not sure how to set any ID for a disk and use that to mount in /etc/fstab. So I'm wondering if my idea even is possible?

So the principle I'm working with is that each of my machines are partially dedicated to running workloads in k3s, about 50-90% each. I use proxmox vms created with https://github.com/Telmate/terraform-provider-proxmox for upgrades and for experimenting with cluster config.

I faced this same error in Ansible instead of Terraform, but it means that one of the parameters given is not accepted. If you are using the Telmate provider, try adding these options to find out which parameter is causing the error. For my case, it was a typo in my IP address string.

Hello guys, For days I'm playing with Telmate/Proxmox Terraform provider/plugin and its very poor experience.

Work stuff. We heavily rely upon terraform-provider-proxmox and by extension proxmox-api-go. Both of those projects need serious love.

I've looked at this in the past and this provider seems to be the one to go with https://github.com/Telmate/terraform-provider-proxmox