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

[Discussion] Proxmox supported versions (and whether to deprecate/drop them) #9199

Open
3 of 5 tasks
Lithimlin opened this issue Nov 26, 2024 · 11 comments
Open
3 of 5 tasks
Labels
module module needs_info This issue requires further information. Please answer any outstanding questions needs_template This issue/PR has an incomplete description. Please fill in the proposed template correctly plugins plugin (any type)

Comments

@Lithimlin
Copy link
Contributor

Lithimlin commented Nov 26, 2024

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:

Older versions of Proxmox will accept a numeric value for size using the storage parameter to automatically choose which storage to allocate from [...]

And while I can find the storage parameter in the API Docs (see the POST 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:

  1. Is support of all Proxmox versions necessary?
  2. Is support of all Proxmox versions desirable?
  3. Does anyone know where I can check what the storage parameter is being used for since the numeric value for disk/rootfs is no longer valid?
  4. Additionally, does anyone know when this behaviour changed? I could narrow it down to somewhere between versions 4.0 and 5.0 using the Proxmox Wiki (old post vs new post).

Issue Type

Discussion

Component Name

proxmox

Additional Information

No response

Code of Conduct

  • I agree to follow the Ansible Code of Conduct
@Lithimlin Lithimlin changed the title [Discussion] Proxmox supported versions (and how to deprecate/drop them) [Discussion] Proxmox supported versions (and whether to deprecate/drop them) Nov 26, 2024
@ansibullbot
Copy link
Collaborator

Files identified in the description:

  • plugins/modules/proxmox

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

@ansibullbot
Copy link
Collaborator

@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:

  • ansible version

Please set the description of this issue with an appropriate template from:
https://github.com/ansible/ansible/tree/devel/.github/ISSUE_TEMPLATE

click here for bot help

@ansibullbot
Copy link
Collaborator

@ansibullbot ansibullbot added module module needs_info This issue requires further information. Please answer any outstanding questions needs_template This issue/PR has an incomplete description. Please fill in the proposed template correctly plugins plugin (any type) labels Nov 26, 2024
@Lithimlin
Copy link
Contributor Author

Moved to the Maintainer Discussions

@Lithimlin
Copy link
Contributor Author

Reopened after finding out that here is the correct to post this after all.

@Lithimlin Lithimlin reopened this Nov 26, 2024
@Lithimlin
Copy link
Contributor Author

It seems that the behavior of using rootfs and storage hasn't changed at all and was simply extended upon (see #9065).
So only the questions regarding the supported versions remain.

@felixfontein
Copy link
Collaborator

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.

@Lithimlin
Copy link
Contributor Author

First off we should probably see if deprecating older support is necessary.
For the specific issue I was having (rootfs and storage), that behavior is still supported in the current API.

The bigger question is whether supporting versions below 4.0 (without LXC support) makes sense.

@Thulium-Drake
Copy link
Contributor

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.

@IamLunchbox
Copy link
Contributor

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.

@Lithimlin
Copy link
Contributor Author

The biggest change would come from dropping support below PVE4.0, since that removes the openvz-type containers in favor of LXCs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module module needs_info This issue requires further information. Please answer any outstanding questions needs_template This issue/PR has an incomplete description. Please fill in the proposed template correctly plugins plugin (any type)
Projects
None yet
Development

No branches or pull requests

5 participants