Most OpenNebula resources have associated permissions for the owner, the users in her group, and others. For each one of these groups, there are three rights that can be set: USE, MANAGE and ADMIN. These permissions are very similar to those of UNIX file system.
Managing Permission through the CLI¶
This is how the permissions look in the terminal:
onetemplate show 0 TEMPLATE 0 INFORMATION ID : 0 NAME : vm-example USER : oneuser1 GROUP : users REGISTER TIME : 01/13 05:40:28 PERMISSIONS OWNER : um- GROUP : u-- OTHER : --- [...]
The previous output shows that for the Template 0, the owner user
oneuser1 has USE and MANAGE rights. Users in the group
users have USE rights, and users that are not the owner or in the
users group don’t have any rights over this Template.
You can check what operations are allowed with each of the USE, MANAGE and ADMIN rights in the xml-rpc reference documentation. In general these rights are associated with the following operations:
- USE: Operations that do not modify the resource like listing it or using it (e.g. using an image or a virtual network). Typically you will grant
USErights to share your resources with other users of your group or with the rest of the users.
- MANAGE: Operations that modify the resource like stopping a virtual machine, changing the persistent attribute of an image or removing a lease from a network. Typically you will grant
MANAGErights to users that will manage your own resources.
- ADMIN: Special operations that are typically limited to administrators, like updating the data of a host or deleting an user group. Typically you will grant
ADMINpermissions to those users with an administrator role.
VirtualMachine objects allow you to set the permission level required for each specific action, for example you may want to require USE for the delete-recreate operation instead the default ADMIN right. You can overrride the default permissions for each action in oned.conf.
By default every user can update any permission group (owner, group or other) with the exception of the admin bit. There are some scenarios where it would be advisable to limit the other set (e.g. OpenNebula Zones so users can not break the group limits). In these situations the
ENABLE_OTHER_PERMISSIONS attribute can be set to
Changing Permissions with chmod¶
The previous permissions can be updated with the chmod command. This command takes an octet as a parameter, following the octal notation of the Unix chmod command. The octet must be a three-digit base-8 number. Each digit, with a value between 0 and 7, represents the rights for the owner, group and other, respectively. The rights are represented by these values:
- The USE bit adds 4 to its total (in binary 100)
- The MANAGE bit adds 2 to its total (in binary 010)
- The ADMIN bit adds 1 to its total (in binary 001)
Let’s see some examples:
onetemplate show 0 ... PERMISSIONS OWNER : um- GROUP : u-- OTHER : --- onetemplate chmod 0 664 -v VMTEMPLATE 0: Permissions changed onetemplate show 0 ... PERMISSIONS OWNER : um- GROUP : um- OTHER : u-- onetemplate chmod 0 644 -v VMTEMPLATE 0: Permissions changed onetemplate show 0 ... PERMISSIONS OWNER : um- GROUP : u-- OTHER : u-- onetemplate chmod 0 607 -v VMTEMPLATE 0: Permissions changed onetemplate show 0 ... PERMISSIONS OWNER : um- GROUP : --- OTHER : uma
Setting Default Permissions with umask¶
The default permissions given to newly created resources can be set:
- Globally, with the DEFAULT_UMASK attribute in oned.conf
- Individually for each User, using the oneuser umask command.
These mask attributes work in a similar way to the Unix umask command. The expected value is a three-digit base-8 number. Each digit is a mask that disables permissions for the owner, group and other, respectively.
This table shows some examples:
Managing Permissions in Sunstone¶
Sunstone offers a convenient way to manage resources permissions. This can be done by selecting resources from a view (for example the templates view) and clicking on the
update properties button. The update dialog lets the user conveniently set the resource’s permissions.
OpenNebula can lock actions on a resource to prevent not intended operations, e.g. to not accidentally delete a VM. By default OpenNebula will lock all operations, but you can provide a fine grain lock by specifying the access level required by the action:
- USE: locks all possible actions.
- MANAGE: locks manage and admin actions.
- ADMIN: locks admin actions.
The following resources can be locked:
oneimage lock 2 oneimage delete 2 [one.image.delete] User  : Not authorized to perform MANAGE IMAGE .
oneimage unlock 2
The user ONEADMIN is not affected by locks and can perform the operation in any case.
Managing ACL Rules¶
The ACL authorization system enables fine-tuning of the allowed operations for any user, or group of users. Each operation generates an authorization request that is checked against the registered set of ACL rules. The core then can grant permission, or reject the request.
This allows administrators to tailor the user roles according to their infrastructure needs. For instance, using ACL rules you could create a group of users that can see and use existing virtual resources, but not create any new ones. Or grant permissions to a specific user to manage Virtual Networks for some of the existing groups, but not to perform any other operation in your cloud. Some examples are provided at the end of this guide.
Please note: the ACL rules is an advanced mechanism. For most use cases, you should be able to rely on the built-in resource permissions and the ACL Rules created automatically when a group is created, and when physical resources are added to a VDC.
Understanding ACL Rules¶
Lets start with an example:
#5 IMAGE+TEMPLATE/@103 USE+MANAGE #0
This rule grants the user with ID 5 the right to perform USE and MANAGE operations over all Images and Templates in the group with id 103.
The rule is split in four components, separated by a space:
- User component is composed only by an ID definition.
- Resources is composed by a list of ‘+’ separated resource types, ‘/’ and an ID definition.
- Rights is a list of Operations separated by the ‘+’ character.
- Zone is an ID definition of the zones where the rule applies. This last part is optional, and can be ignored unless OpenNebula is configured in a federation.
The ID definition for User in a rule is written as:
#<id> :for individual IDs
@<id> :for a group ID
* :for All
The ID definition for a Resource has the same syntax as the ones for Users, but adding:
%<id> :for cluster IDs
Some more examples:
This rule allows all users in group 105 to create new virtual resources:
@105 VM+NET+IMAGE+TEMPLATE/* CREATE
The next one allows all users in the group 106 to use the Virtual Network 47. That means that they can instantiate VM templates that use this network.
@106 NET/#47 USE
Note the difference between
* NET/#47 USE" vs
* NET/@47 USE
All Users can use NETWORK with ID 47 vs All Users can use NETWORKS belonging to the Group whose ID is 47
The following one allows users in group 106 to deploy VMs in Hosts assigned to the cluster 100
@106 HOST/%100 MANAGE
Managing ACL Rules via Console¶
The ACL rules are managed using the oneacl command. The ‘oneacl list’ output looks like this:
oneacl list ID USER RES_VHNIUTGDCOZSvRMA RID OPE_UMAC ZONE 0 @1 V--I-T---O-S---- * ---c * 1 * ----------Z----- * u--- * 2 * --------------MA * u--- * 3 @1 -H-------------- * -m-- #0 4 @1 --N----D-------- * u--- #0 5 @106 ---I------------ #31 u--- #0
The rules shown correspond to the following ones:
@1 VM+IMAGE+TEMPLATE+DOCUMENT+SECGROUP/* CREATE * * ZONE/* USE * * MARKETPLACE+MARKETPLACEAPP/* USE * @1 HOST/* MANAGE #0 @1 NET+DATASTORE/* USE #0 @106 IMAGE/#31 USE #0
The first five were created on bootstrap by OpenNebula, and the last one was created using oneacl:
oneacl create "@106 IMAGE/#31 USE" ID: 5
The ID column identifies each rule’s ID. This ID is needed to delete rules, using ‘oneacl delete <id>’.
Next column is USER, which can be an individual user (#) or group (@) id; or all (*) users.
The Resources column lists the existing Resource types initials. Each rule fills the initials of the resource types it applies to.
V : VM
H : HOST
N : NET
I : IMAGE
U : USER
T : TEMPLATE
G : GROUP
D : DATASTORE
C : CLUSTER
O : DOCUMENT
Z : ZONE
S : SECURITY GROUP
v : VDC
R : VROUTER
M : MARKETPLACE
A : MARKETPLACEAPP
RID stands for Resource ID, it can be an individual object (#), group (@) or cluster (%) id; or all (*) objects.
The next Operations column lists the allowed operations initials.
U : USE
M : MANAGE
A : ADMIN
C : CREATE
And the last column, Zone, shows the zone(s) where the rule applies. It can be an individual zone id (#), or all (*) zone.
Managing ACLs via Sunstone¶
Sunstone offers a very intuitive and easy way of managing ACLs.
Select ACLs in the left-side menu to access a view of the current ACLs defined in OpenNebula:
This view is designed to easily understand what the purpose of each ACL is. You can create new ACLs by clicking on the
New button at the top. A dialog will pop up:
In the creation dialog you can easily define the resources affected by the rule and the permissions that are granted upon them.
How Permission is Granted or Denied¶
Visit the XML-RPC API reference documentation for a complete list of the permissions needed by each OpenNebula command.
For the internal Authorization in OpenNebula, there is an implicit rule:
- The oneadmin user, or users in the oneadmin group are authorized to perform any operation.
If the resource is one of type
DOCUMENT the object’s permissions are checked. For instance, this is an example of the oneimage show output:
oneimage show 2 IMAGE 2 INFORMATION ID : 2 [...] PERMISSIONS OWNER : um- GROUP : u-- OTHER : ---
The output above shows that the owner of the image has
If none of the above conditions are true, then the set of ACL rules is iterated until one of the rules allows the operation.
An important concept about the ACL set is that each rule adds new permissions, and they can’t restrict existing ones: if any rule grants permission, the operation is allowed.
This is important because you have to be aware of the rules that apply to a user and his group. Consider the following example: if a user #7 is in the group @108, with the following existing rule:
@108 IMAGE/#45 USE+MANAGE
Then the following rule won’t have any effect:
#7 IMAGE/#45 USE