Feature #1857

Flexible Configuration of Sunstone Interface Plugins/Features

Added by Gary Cuozzo over 8 years ago. Updated about 8 years ago.

Status:ClosedStart date:04/02/2013
Priority:NormalDue date:
Assignee:Daniel Molina% Done:


Target version:-
Resolution: Pull request:


Reference: http://lists.opennebula.org/pipermail/users-opennebula.org/2013-March/022466.html

In order to support a wide range of users with varying levels of technical expertise or requirements, it is desirable to be able to configure the Sunstone GUI to limit the plugins and the capabilities which are presented to users.

The sunstone-plugins.yaml file is a good start and I have successfully used this file to strip out certain modules based on group membership. However, one limitation I encountered was related to disabling the configuration tab. This tab is required to be included or other features of the GUI will break, such as VNC access.

A nice extension to the enable/disable on a plugin basis would be to have each plugin support additional ACL's related to specific functionality within a module. This way, specific modules can be left enabled, but still limit the functions users can access. For example: On the Configuration tab, allow the users to set their preference for language, but not be able to change the secure websockets setting.


#1 Updated by Daniel Molina about 8 years ago

  • Status changed from New to Closed
  • Assignee set to Daniel Molina

This functionality will be included in the new OpenNebula 4.0.

Thank you for your feedback

Also available in: Atom PDF