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

Change how VMID is implemented #118

Open
1 task done
TeYroXOfficial opened this issue Oct 27, 2024 · 3 comments
Open
1 task done

Change how VMID is implemented #118

TeYroXOfficial opened this issue Oct 27, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@TeYroXOfficial
Copy link

Is there an existing feature request for this?

  • I have searched the existing issues before opening this feature request.

Describe the feature you would like to see.

Instead of using random VMID, use next id's for each new server.

Describe the solution you'd like.

Check out:
https://pve.proxmox.com/pve-docs/api-viewer/index.html#/cluster/nextid and use it for new servers

Additional context to this request.

No response

@TeYroXOfficial TeYroXOfficial added the enhancement New feature or request label Oct 27, 2024
@Adekabang
Copy link
Contributor

Also, it could be better if we could set a certain range like vm only in the range between 1000 and 1999

@staalexa
Copy link

How would that benefit anyone? As long as the IDs are unique…

@Adekabang
Copy link
Contributor

In my use case, random could be fine as long as in a certain range, but the range helps to map easily like VM for production and development, the other way is to assign the VM with a tag, but needs manually assigned in Proxmox.

Other than that, if I do a temporary migration, I could map the VM back to the original node, since the convoy has not handled migration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants