Anyone know of a way to add/remove multiple VMIDs from a tag in one batch go? I'm only really seeing the capabilities to add/remove a tag one VMID at a time.
qm set 3001 --tags 1
update VM 3001: -tags 1
cat /etc/pve/qemu-server/3001.conf |grep tag
tags: 1
qm set 3001 --tags 2
update VM 3001: -tags 2
cat /etc/pve/qemu-server/3001.conf |grep tag
tags: 2
qm set 3001 --tags 1,2
update VM 3001: -tags 1,2
cat /etc/pve/qemu-server/3001.conf |grep tag
tags: 1;2
There is no GUI interface to do what you want, today.Yeah really was wanting something GUI since I'm sure with API and CLI aspects you can just wrap scripting around it to your heart's content.
There is no GUI interface to do what you want, today.
Latest PVE has new "TAG View" - which is great, IMHO. But not what you want.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
I realized this - but see OP's request.if you don't preserve existing tags, they will be overwritten/lost.
I know the feeling! But we sometimes need reminding that we are using Linux.Yeah really was wanting something GUI
Of course. I just meant that handling tags from CLI/API needs to be done carefully. If one is assured to always only have one tag - easy method works. But if you are making a general solution, then there needs to be logic to handle tag concatenation, or one of many removal.To be able to preserve existing tag/s - they could be read by script/command & added etc.
I realized this - but see OP's request.
To be able to preserve existing tag/s - they could be read by script/command & added etc.
I know the feeling! But we sometimes need reminding that we are using Linux.
For the next major rev of PVE, maybe change tag storage to a simple (non-sql) DB?Hi,
you could open a feature request on our bugtracker (or see if there is already one): https://bugzilla.proxmox.com
though i can't make any promises. One underlying issue is that the tags are saved in the respective vm configs, thus editing multiple at once would mean to lock multiple vm configs either all at once or shortly one after the other. also only one the node housing the vm is allowed to change that config.
we could *maybe* do something in the ui (e.g. loop over the selected vms, etc.) but not sure where we would place such a ui feature. in any case, it'd probably be better to discuss such things on the bug tracker for better developer visibility
Hi,
you could open a feature request on our bugtracker (or see if there is already one): https://bugzilla.proxmox.com
though i can't make any promises. One underlying issue is that the tags are saved in the respective vm configs, thus editing multiple at once would mean to lock multiple vm configs either all at once or shortly one after the other. also only one the node housing the vm is allowed to change that config.
we could *maybe* do something in the ui (e.g. loop over the selected vms, etc.) but not sure where we would place such a ui feature. in any case, it'd probably be better to discuss such things on the bug tracker for better developer visibility
i can see that being an option for the tree. basically just group untagged guests (a separate bugzilla entry would be nice so we can track it easier)I'd be great to have default "untagged" tag that would group all untagged VMs.
yeah at least for nodes there is already a feature request: https://bugzilla.proxmox.com/show_bug.cgi?id=5865Being able to add a tag to storage pool would also cleanup the tree, imho.
not sure what you mean exactly here... what do you mean with 'tag-group-view' ?Then, you would need multi-select in a tag-group view (on the right) so tags at the top could be changed - easy for me to design
we could change how we save the tags, but we have to backwards compatible (or find a good way to automatically convert it) which is not the easiest taskFor the next major rev of PVE, maybe change tag storage to a simple (non-sql) DB?
good, just so you know if more people reply to a bug with new info (e.g. a new usecase or a new explanation why that's important) it's more visible to us (but please don't just add a '+1' comment , instead just subscribe to the bug)Looks like a request is already open on this topic and has been open since last year -> https://bugzilla.proxmox.com/show_bug.cgi?id=4932
@gfngfn256 , its not that simple unfortunately.
Code:qm set 3001 --tags 1 update VM 3001: -tags 1 cat /etc/pve/qemu-server/3001.conf |grep tag tags: 1 qm set 3001 --tags 2 update VM 3001: -tags 2 cat /etc/pve/qemu-server/3001.conf |grep tag tags: 2 qm set 3001 --tags 1,2 update VM 3001: -tags 1,2 cat /etc/pve/qemu-server/3001.conf |grep tag tags: 1;2
as you can see, if you don't preserve existing tags, they will be overwritten/lost.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
qm set
command. If you add an existing tag again, nothing bad will happen.qm set $vmid --tags $(qm config $vmid | grep tags: | cut -c 7-),$newtag
I meant the new "Tag View" option. The widget for multi-edit could be similar to "HA>Groups>Create" with checkmarks. Or something like a dual panel where left is "add tag" and right is "remove" (like a MS office toolbar change widget).not sure what you mean exactly here... what do you mean with 'tag-group-view' ?