Feature #2838
Spell out in docs that restricted attrs are check for non-oneadmin VM templates.
| Status: | Closed | Start date: | 04/16/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Tino Vázquez | % Done: | 100% | |
| Category: | Documentation | |||
| Target version: | Release 4.8 | |||
| Resolution: | fixed | Pull request: |
Description
Reported in the mailing list:
http://lists.opennebula.org/pipermail/users-opennebula.org/2014-April/027131.html
Hello,
http://docs.opennebula.org/4.4/administration/references/oned_conf.html#oned-conf-restricted-attributes-configuration
says we can use {VM,IMAGE}_RESTRICTED_ATTR
to restrict users outside the oneadmin groupbut I experiment as a user whose group is users, not oneadmin
to launch a VM from a vm.template with CONTEXT/FILES
and onevm disk-snapshot command which must use SOURCE attribute,
both work, i.e. restricted_attr do not seem to work..
History
#1
Updated by Ruben S. Montero about 7 years ago
- Tracker changed from Bug to Feature
- Subject changed from restricted attributes are ignored to Spell out in docs that restricted attrs are check for non-oneadmin VM templates.
- Category changed from Core & System to Documentation
- Status changed from Pending to New
- Priority changed from High to Normal
#2
Updated by Ruben S. Montero about 7 years ago
- Target version changed from Release 4.6 to Release 4.8
#3
Updated by Tino Vázquez almost 7 years ago
- Status changed from New to Closed
- Assignee set to Tino Vázquez
- % Done changed from 0 to 100
- Resolution set to fixed
Restricted attributed better explained in the documentation