Hi Marco, I faced a similar problem and we ended up using different storages for different groups of people like this:
ZFS base and Proxmox VE with different groups, e.g. group1 rpool/group1/data (for KVM and LXC) rpool/group1/local as filesystem for templates rpool/general/local as filesystem for templates, but the general ones So every group member "sees" their own templates and the general ones already downloaded. We build a lot of templates automatically on a per day basis, so that our own are always up to date. Not a perfect solution like your proposed, but it works. On Wed, Jan 11, 2017 at 1:57 PM, Marco M. Gabriel <marcomgabr...@gmail.com> wrote: > Hi, > > there are two container repositories included in Proxmox since years: > Proxmox' own repository and the Turnkey Linux repository. > > I would like to discuss about two things: > > 1. I got a few customer requests over the last years if they could enable > their own repository. Currently, this is only possible if they'd change the > APLInfo.pm and possibly some more code and it wouldn't be update safe. > > A fine solution would be to include additional repositories from a file > located in /etc/pve - for example /etc/pve/pct-repos.cfg. > > 2. How do you think about including more "global" repositories? > > What would someone need to provide to get listed in the global repos? > > If I'm totally wrong here with my request, just let me know where to ask > those questions. > > Thanks, > Marco > _______________________________________________ > pve-devel mailing list > pve-devel@pve.proxmox.com > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel