Hello,
I have been spending the last couple of days making a Vagrant-provider plugin work, which seems to have been originally created by a German company called TelCat GmbH (no longer exists). The code base is outdated: https://github.com/SecSamDev/vagrant-proxmox
After creating a legacy Ubuntu 18.04 dev environment and spending countless hours messing with the dependencies and fixing parts of the code, I got it to run using an API key instead of the original username-password method of authentication.
Then I proceeded to creating compatible Vagrant images with the default username/password and SSH keys as explained here.
Up to this point, I am doing this not just for fun but because I wanted to explore the concept of Hashicorp Vagrant Boxes and how it applies to Proxmox. Namely, the ability to both:
1. Spin up a VM/LXC container from a filesystem image (not requiring any installation)
2. Supply cloud-init config
3. Provision additional services using scripts and playbooks which might require a base functionality (provided through cloud-init)
Is evidently very valuable, especially when combined with the ability to maintain SSH tunnels and port-forwarding setups.
However, I am starting to question the value of Vagrant in this case, since, just as easily (I am guessing), I can use Ansible itself (with the community.general.proxmox module) to accomplish the first point above.
Is there a value in fixing and maintaining the Vagrant provider? I am also not very clear on whether I want to support Hashicorp. I am worried about anti-features and the use of anti-features in projects claimed to be free and open-source.
As far as I can see, the value of Vagrant comes not from its codebase but rather the big library of Cloud boxes. However, according to what I have been reading, these boxes are provider specific, which makes the case for Vagrant even weaker.
Since I am new to Proxmox, cloud-init, Vagrant, and Ansible, I would appreciate general thoughts and insight in any direction. It does not have to be a very structured discussion. I just want to learn about the patterns that others use and what works in leveraging and automating Proxmox, possibly for profit and for operating cloud services.
In relation to this discussion is the best way you guys know of to spin up a VM from a filesystem image, hence replicating the net effect of using Vagrant (avoiding installation and having a predictable/accessible base for provisioning and automation). Is it possible to do this in one step using the API or do you recommend using the `qm importdisk` from the command line. Thanks!
I have been spending the last couple of days making a Vagrant-provider plugin work, which seems to have been originally created by a German company called TelCat GmbH (no longer exists). The code base is outdated: https://github.com/SecSamDev/vagrant-proxmox
After creating a legacy Ubuntu 18.04 dev environment and spending countless hours messing with the dependencies and fixing parts of the code, I got it to run using an API key instead of the original username-password method of authentication.
Then I proceeded to creating compatible Vagrant images with the default username/password and SSH keys as explained here.
Up to this point, I am doing this not just for fun but because I wanted to explore the concept of Hashicorp Vagrant Boxes and how it applies to Proxmox. Namely, the ability to both:
1. Spin up a VM/LXC container from a filesystem image (not requiring any installation)
2. Supply cloud-init config
3. Provision additional services using scripts and playbooks which might require a base functionality (provided through cloud-init)
Is evidently very valuable, especially when combined with the ability to maintain SSH tunnels and port-forwarding setups.
However, I am starting to question the value of Vagrant in this case, since, just as easily (I am guessing), I can use Ansible itself (with the community.general.proxmox module) to accomplish the first point above.
Is there a value in fixing and maintaining the Vagrant provider? I am also not very clear on whether I want to support Hashicorp. I am worried about anti-features and the use of anti-features in projects claimed to be free and open-source.
As far as I can see, the value of Vagrant comes not from its codebase but rather the big library of Cloud boxes. However, according to what I have been reading, these boxes are provider specific, which makes the case for Vagrant even weaker.
Since I am new to Proxmox, cloud-init, Vagrant, and Ansible, I would appreciate general thoughts and insight in any direction. It does not have to be a very structured discussion. I just want to learn about the patterns that others use and what works in leveraging and automating Proxmox, possibly for profit and for operating cloud services.
In relation to this discussion is the best way you guys know of to spin up a VM from a filesystem image, hence replicating the net effect of using Vagrant (avoiding installation and having a predictable/accessible base for provisioning and automation). Is it possible to do this in one step using the API or do you recommend using the `qm importdisk` from the command line. Thanks!
Last edited: