Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Allow Specification of Proxmox Version for Installation #256

Open
thystips opened this issue Aug 23, 2024 · 4 comments
Open

Comments

@thystips
Copy link
Collaborator

Hello,

First of all, thank you for maintaining this project, it's been extremely helpful in automating my deployments.

I would like to request a feature that allows users to specify the exact version of Proxmox to install during the setup process. In my specific use case, I deploy tools that are only compatible with certain minor versions of Proxmox. Therefore, being able to define the Proxmox version is crucial to ensure compatibility and avoid potential issues.

Currently, the role installs the latest available version, which may lead to incompatibilities with certain tools or scripts that haven't been updated to work with newer releases. By enabling version specification, users can ensure that their deployments are stable and consistent across different environments.

Thank you for considering this feature.

@lae
Copy link
Owner

lae commented Aug 23, 2024

This is likely going to be very tricky, I think. I can't think up off the top of my head how one would grab a specific "minor" version from the apt repositories for all relevant packages. If you have any information regarding how to go about this, if upstream PVE even makes it possible (e.g. if old releases are not pruned), that'd be helpful.

@thystips
Copy link
Collaborator Author

After checking the PVE repository, it appears that multiple versions are available for each package. This suggests that it should be possible to specify a particular version to install with Ansible.

As a workaround for my specific use case, I could use a custom repository with tailored packages, but this approach is less generalizable. I believe allowing version specification directly in the role would be a more flexible solution.

@lae
Copy link
Owner

lae commented Aug 24, 2024

Yeah but like, my concern is that there isn't a way to pin all packages to an associated minor version. You can install a specific version of a single package, in our case proxmox-ve1, but what about its dependencies? For example proxmox-ve 8.2.0 depends on pve-qemu-kvm whose latest is 9.0.2. Pulling proxmox-ve=8.1.0 is still gonna pull pve-qemu-kvm=9.0.2, which sounds like it might cause issues?

Footnotes

  1. https://github.com/lae/ansible-role-proxmox/blob/develop/tasks/identify_needed_packages.yml#L5

@thystips
Copy link
Collaborator Author

thystips commented Aug 24, 2024

You're right, version need to be set on proxmox-ve, pve-kernel and pve-qemu-kvm but if a strict version is set for proxmox-ve in _pve_install_packages, pve_extra_packages can be used for other packages without add complexity in role.
Is it a better way ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants