Is is possible in the left hand section where it shows the data center and host views to create a folder where you can place the templates so they don't show up in the container and vm section? I think this would make it much easier to read and keep things organized and clean?
Templates
- Thread starter Pinochet
- Start date
Ok, this is what I mean. kvm/ct templates is what I'd like to store in a folder for just them in the UI. I've converted a few ct and vm to templates and they show up in the same tree that list the other containers and vm/s. I'd like to not only have templates separated out into their own respective section in the gui but it would also be nice to keep vm/s and ct/s separated into their own sections if one desires. I remember doing this in esxi where you could create sections and name them like "containers" or "vm/s" and put them into there to keep the UI really clean. It looks like folder view kinda does this but even then it still shows the containers and the container templates together. I'd like to be able to right click in the UI and create another folder in the section I'm in ..for example in the container section. Then I could create a template folder to put the templates in there. Or create multiple folders like "Templates for engineering" "Templates for devops" "Templates for deployment" etc. I'm not sure how the UI looks when clustered as I only have one host but the same would go for storage / networks etc.
Sometimes you have to go with what the system is capable of, so this is how we do it:
I seldomly use KVM templates as such, I just use VMs due to the fact that templates are not runnable and updateable. I just use "normal" VMs in a template folder and do regular Windows maintenance updates every month on them. For Linux, we just do network PXE installs which is faster than clone, update, cleanup and specialize with a local mirror and years of automation experience.
For containers we have an external system that is able to keep container templates up to date and provides general and special containers in their own storage inside PVE so that you can choose from which container template storage you can take your template while creating a new container.
I seldomly use KVM templates as such, I just use VMs due to the fact that templates are not runnable and updateable. I just use "normal" VMs in a template folder and do regular Windows maintenance updates every month on them. For Linux, we just do network PXE installs which is faster than clone, update, cleanup and specialize with a local mirror and years of automation experience.
For containers we have an external system that is able to keep container templates up to date and provides general and special containers in their own storage inside PVE so that you can choose from which container template storage you can take your template while creating a new container.
"Sometimes you have to go with what the system is capable of, so this is how we do it:"
True but you can always improve which is what my post was about.
There are generally two ways to request improvement to PVE:
- File an entry here: https://bugzilla.proxmox.com/ . Try to provide as much supporting information as possible
- Get involved: https://www.proxmox.com/en/proxmox-ve/get-involved
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox