Skip to content

F OpenNebula/one#6394: update documentation for issue 6394 #845

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aaizel1 wants to merge 1 commit into
base: one-7.4-maintenance
Choose a base branch
from
+5 −3
Open

F OpenNebula/one#6394: update documentation for issue 6394 #845

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions content/product/cloud_system_administration/multitenancy/manage_groups.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,9 +67,11 @@ To delete a user from a group, just move the user back to the default `users` gr

Upon group creation, a special admin user account can be defined. This admin user will only have administrative privileges for the new group, not for all the resources in the OpenNebula cloud as the ‘oneadmin’ group users have.

Another aspect that can be controlled when a group is created is the type of resources that group users will be allowed to create.
Another aspect that can be controlled when a group is created or updated is the type of resources that group users will be allowed to create or view.

This can be managed visually in Sunstone and can also be managed through the CLI. In the latter, details of the group are passed to the `onegroup create` command as arguments. This table lists the description of said arguments.
In Sunstone, these permissions are configured in the **Permissions** step of the group creation and update forms. Saving the form creates or updates the corresponding ACL rules automatically, so the ACL tab does not need to be used for these standard group permissions.

Creation permissions can also be configured through the CLI. In this case, details of the group are passed to the `onegroup create` command as arguments. This table lists the description of said arguments.

| Argument | M / O | Value | Description |
|---------------------|-----------|--------------------|------------------------------------------------------------------------------|
Expand Down Expand Up @@ -136,7 +138,7 @@ You can read more about OpenNebula permissions in the [Managing Permissions]({{%

## Resource Sharing

When a new group is created the cloud administrator can define if the users of this view will be allowed to view the VMs and Services of other users in the same group. If this option is checked a new ACL rule will be created to give users in this group access to the VMS and Services in the same group. Users will not able to manage these resources but they will be included in the list views of each resource.
When a group is created or updated, the cloud administrator can select the resource types that group users will be allowed to view when those resources belong to the same group. These options are available under **View** in the **Permissions** step. Saving the form creates or updates the corresponding ACL rules automatically. Users will be able to access and list the selected resources, but they will not be able to manage them.

{{< image
pathDark="/images/sunstone/groups/dark/group_permissions.png"
Expand Down
Loading