-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[Discussion] Proxmox supported versions (and whether to deprecate/drop them) #9199
Comments
Files identified in the description:
If these files are incorrect, please update the |
@Lithimlin: Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information. Here are the items we could not find in your description:
Please set the description of this issue with an appropriate template from: |
Moved to the Maintainer Discussions |
Reopened after finding out that here is the correct to post this after all. |
It seems that the behavior of using |
Right now the module supports all Proxmox versions it did support in the past, since it doesn't mention which versions it supports. To change this, it's necessary to deprecate support for older versions, so we can officially drop support for them in the next (or second next) major release of community.general. |
First off we should probably see if deprecating older support is necessary. The bigger question is whether supporting versions below 4.0 (without LXC support) makes sense. |
I don't see an issue with deprecating versions that are no longer maintained by Proxmox themselves. That doesn't have to mean that we actively remove stuff or change stuff that no longer is supported. But it can allow changes to the modules that might break on older versions of the API. |
I think it is not strictly necessary, since apparently proxmox themselves try to keep breaking changes to a minimum. But since proxmox does have a clear support policy, I think it does not harm either to adhere to their policy - especially since they might deprecate features in the future. |
The biggest change would come from dropping support below PVE4.0, since that removes the |
Summary
To work on some issues, I am currently refactoring the
proxmox
module.While working on that, it came up again and again that technically, any version of Proxmox, even below 4.0 is supported. This raised the question for me on whether this is 1) necessary or 2) even desirable. The Debian versions those old Proxmox versions are based on are long at their EOL and get no more (security) updates.
This particularly came up when trying to figure out how the
storage
parameter works now.In the module docs, it says for the
disk
parameter:And while I can find the
storage
parameter in the API Docs (see thePOST
tab), I cannot figure out if/for what it is even still being used now. This is not necessarily a problem regarding supported versions, but further complicates the existing issues.To summarize, my main questions are:
storage
parameter is being used for since the numeric value fordisk
/rootfs
is no longer valid?Issue Type
Discussion
Component Name
proxmox
Additional Information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: