Hi, First thanks for this work!
Second, It looks like some links got scrambled up - maybe through the fault of your mail editor. I tried to fix them in this reply here: On 10/04/2017 02:19 AM, Musee Ullah wrote: > Hey all, > > It's been a while. I just a cut a release of an Ansible role that now > supports deploying PVE 5.x nodes (it still supports 4.x), as well as > configuring HTTPS certificates for the nodes. Most of the requests from > the previous email thread (back in March) were also implemented long > ago, but I happened to not cut a release for them until now. (For more > info, check the releases page: https://github.com/lae/ansible-role-prox > mox/releases.) > <https://github.com/lae/ansible-role-proxmox/releases> > You can see a successful test deployment of 5.x/Debian Stretch here: ht > tps://travis-ci.org/lae/ansible-role-proxmox/jobs/282937447#L4975 - > I've also successfully tested creating a cluster with pvecm locally > using this (I'll eventually add this functionality into the Ansible > role). > <https://travis-ci.org/lae/ansible-role-proxmox/jobs/282937447#L4975> > Anyway, if any of you have time to do a 5.x deployment (or even manage > an existing 4.x deployment) using this role, I'd love to get your input > as to what could be improved. > > The role is available on Ansible Galaxy at https://galaxy.ansible.com/l > ae/proxmox/ (the README tab has a quickstart section with an example > single host deployment). > <https://galaxy.ansible.com/lae/proxmox/> > Also one more thing to note - this can easily be used to keep 4.x and > 5.x clusters up to date (it'll upgrade to the latest in their series) - > but it can't be used for automating an upgrade from 4.x to 5.x (too > many variables to consider, honestly). > > cheers, Thomas _______________________________________________ pve-user mailing list [email protected] https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
