Is it possible to configure a Tag color as Syntax instead of each Tag individually?

[Anotheruser]

Pretty much the question, lets say i got a lot of similar Tags that should all have the same color,
exampletag1, exampletag2, exampletag3 etc, is there a way to specify that all of them and the following should have the same color?
like exampletag*:333300:FFFFFF;
I dont mind doing it in the configs.
This is very simplified, we are planing to use this for certain vm types that can have ranges for multiple million and we dont want to manually go to the tag section everytime we are creating a new type, so alternative would be to just use a script and specify every possibility upfront.
How does proxmox handle a lot of "tag-style" entries in the datacenter.cfg? like 4 million?
any help appreciated

 

[dcsapak]

exampletag1, exampletag2, exampletag3 etc, is there a way to specify that all of them and the following should have the same color?

currently no, you have to set the color for each one

This is very simplified, we are planing to use this for certain vm types that can have ranges for multiple million and we dont want to manually go to the tag section everytime we are creating a new type, so alternative would be to just use a script and specify every possibility upfront.

what do you mean by this, do you want to have multiple million tags per vm?

How does proxmox handle a lot of "tag-style" entries in the datacenter.cfg? like 4 million?

probably not, because there is an upper file limit on /etc/pve of 1 MiB, and since you need more than 2 bytes per tag this won't work

IMHO it sounde like you want to use the tags for things it's not really designed for
wouldn't it be better to have an external (e.g. config management) system that has the data saved you need?

what is it exactly that you want to achieve?

 

[Anotheruser]

what do you mean by this, do you want to have multiple million tags per vm?

what is it exactly that you want to achieve?

thanks for the responds.

We are not planing to have more than 3-4 Tags assigned to one VM at the same time.

Our original idea was to create different Standards / Types for vms with according vm templates,
lets say we have a VM Type "L0015G2" (Linux Number 15 Generation 2), this standard then includes certain settings in proxmox (like, ovmf, virtio network, virtio scsi controller etc) or stuff inside the vm (like software X is installed and configured in a way etc) that all vms of that type need to follow / we can then rely that the vms are setup in a certain way if we are doing maintenance etc, all those things are listed in our documentaion / resource management (this system already exists).
The tags would be in our opinion the best way to integrate that system into proxmox, bc it would allow for easy searching / filtering of vms according to their type and also allow for a very fast identification of the general setup / settings of a vm.
We cant really use the pools / groups for this bc thats used for grouping vms depending on what they are used for / what they are doing.
And just putting it in the vm name also isnt a great solution (like vmname.L0015G2)

And since we are already using tags for 3-4 other purposes we wanted to separate them by color. (like all vm standard / typ tags in grey)
And we didnt want to have to set the style for each new typ / standard manually, so the idea was to just create sth like L****G* and W****G*
to have all tags that fit that in the same color.

Anyway we are probably just going to write a script that checks our docu and then automatically creates the tags / styles in proxmox if it sees a new one.

Feel free to suggest a better way how a type system like this could be implemented

 

[dcsapak]

ok that makes kind of sense, but how did you arrive at the '4 million' part ? even if you have 10 tags per vm assigned, and not one tag is reused, you'd need 400000 guests to reach that

 

[Anotheruser]

ok that makes kind of sense, but how did you arrive at the '4 million' part ? even if you have 10 tags per vm assigned, and not one tag is reused, you'd need 400000 guests to reach that

if you include potential future vm tags even if this standard / type doesnt (yet) exist, the plan basically was to upfront create all possible tags that would be allowed under this system. L0001G1 to L9999G99 which is 9999*99 = 989901 each and then another one with W for Windows, B for BSD and O for Other makes a little under 4 Million. Also the cluster currently has around 1800 VMs (a lot of testenvironments that might be spun up once a year or so), but they need to be ready if needed regardless, so quite a lot of things going on.

Other think, it would be amazing for setups like this to have the possibility to do certain bulk action on a tag or search result base, like restarting, migrating and backups.