From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Alejandro Bonilla <abonilla@suse.com>
Subject: Re: [PVE-User] Automation - salt/ansible/terraform...
Date: Sat, 3 Oct 2020 14:06:35 +0200 [thread overview]
Message-ID: <7c8c487e-52f1-7ee3-6d1e-82cdd982ed13@proxmox.com> (raw)
In-Reply-To: <BB4B29FC-E50C-43A4-AB8E-563D04FA8578@suse.com>
Hi,
On 02.10.20 14:55, Alejandro Bonilla wrote:
> Is there any provisioning/cm tool that works best with PVE? I’ve tried salt-cloud without great success and I’m open to use anything else that helps me automating VM provisioning + post-deploy tasks. Any sample configs are also appreciated…
There are various plugins for Proxmox VE provided by automation projects
themselves and/or their community.
Terraform:
https://github.com/Telmate/terraform-provider-proxmox
Ansible:
https://docs.ansible.com/ansible/latest/collections/community/general/proxmox_module.html
https://github.com/lae/ansible-role-proxmox
Salt:
https://docs.saltstack.com/en/latest/topics/cloud/proxmox.html
They normally provide some documentation or examples.
In my experience, the Proxmox VE uses lots of different automation
tools, most of the time whatever they use already for other tasks.
That's why I personally, and also some other devs here, use ansible, not
necessarily because it or the support for it is better, but because those
have it already in use to manage infrastructure and some private stuff.
For a commercial VM/CT offering, there are also plugins for shop or
billing systems like WHCMS.
hope that helps!
cheers,
Thomas
prev parent reply other threads:[~2020-10-03 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 12:55 Alejandro Bonilla
2020-10-03 12:06 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c8c487e-52f1-7ee3-6d1e-82cdd982ed13@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=abonilla@suse.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox