Fixing role names to match code

This commit is contained in:
Anne Gentle 2011-05-19 12:17:55 -05:00
parent ff08fcb024
commit 91e685e359
2 changed files with 5 additions and 5 deletions

View File

@ -6,7 +6,7 @@ nova-manage
control and manage cloud computer instances and images control and manage cloud computer instances and images
------------------------------------------------------ ------------------------------------------------------
:Author: nova@lists.launchpad.net :Author: openstack@lists.launchpad.net
:Date: 2010-11-16 :Date: 2010-11-16
:Copyright: OpenStack LLC :Copyright: OpenStack LLC
:Version: 0.1 :Version: 0.1
@ -121,7 +121,7 @@ Nova Role
nova-manage role <action> [<argument>] nova-manage role <action> [<argument>]
``nova-manage role add <username> <rolename> <(optional) projectname>`` ``nova-manage role add <username> <rolename> <(optional) projectname>``
Add a user to either a global or project-based role with the indicated <rolename> assigned to the named user. Role names can be one of the following five roles: admin, itsec, projectmanager, netadmin, developer. If you add the project name as the last argument then the role is assigned just for that project, otherwise the user is assigned the named role for all projects. Add a user to either a global or project-based role with the indicated <rolename> assigned to the named user. Role names can be one of the following five roles: cloudadmin, itsec, sysadmin, netadmin, developer. If you add the project name as the last argument then the role is assigned just for that project, otherwise the user is assigned the named role for all projects.
``nova-manage role has <username> <projectname>`` ``nova-manage role has <username> <projectname>``
Checks the user or project and responds with True if the user has a global role with a particular project. Checks the user or project and responds with True if the user has a global role with a particular project.

View File

@ -38,11 +38,11 @@ Role-based access control (RBAC) is an approach to restricting system access to
Novas rights management system employs the RBAC model and currently supports the following five roles: Novas rights management system employs the RBAC model and currently supports the following five roles:
* **Cloud Administrator.** (admin) Users of this class enjoy complete system access. * **Cloud Administrator.** (cloudadmin) Users of this class enjoy complete system access.
* **IT Security.** (itsec) This role is limited to IT security personnel. It permits role holders to quarantine instances. * **IT Security.** (itsec) This role is limited to IT security personnel. It permits role holders to quarantine instances.
* **Project Manager.** (projectmanager)The default for project owners, this role affords users the ability to add other users to a project, interact with project images, and launch and terminate instances. * **System Administrator.** (sysadmin)The default for project owners, this role affords users the ability to add other users to a project, interact with project images, and launch and terminate instances.
* **Network Administrator.** (netadmin) Users with this role are permitted to allocate and assign publicly accessible IP addresses as well as create and modify firewall rules. * **Network Administrator.** (netadmin) Users with this role are permitted to allocate and assign publicly accessible IP addresses as well as create and modify firewall rules.
* **Developer.** This is a general purpose role that is assigned to users by default. * **Developer.** (developer) This is a general purpose role that is assigned to users by default.
RBAC management is exposed through the dashboard for simplified user management. RBAC management is exposed through the dashboard for simplified user management.