Ability for admins to lock certain templates, hostgroups, and disk layouts from editing
I'm setting up a server for use by multiple organizations.
I'd like to provide them with access to some base working kickstarts, snippets, pxe templates, disk layouts, and hostgroups to get them started.
At the same time I am expecting at least some people will want to create, edit, and delete templates, but I fully expect that if I give full access someone is going to break one of the ones shared to all.
So my options seem to be either revoking at least edit/delete which makes create less appealing as well or making 13 copies of each (13 orgs times 8 templates/layouts off the top of my head) template, disk layout, and hostgroup we use for each org, so they will only harm their own org if they break something.
Neither seems like a very good approach.
#6 Updated by Marek Hulán over 3 years ago
- Description updated (diff)
- Status changed from New to Resolved
I think one can achieve all of that already with granular permission system and in case of partition tables and provisioning templates, one could even use the locking mechanism. Please let me know if I misunderstood the request, I'd reopen the issue.