The Compute documentation (http://www.openstack.org/software/openstack-compute/) clearly states "Dashboard with fully integrated support for self-service provisioning".
It also states that multiple roles are allowed per project. "A user can be assigned different roles in different tenants: for example, Alice may also have the "admin" role in the "Cyberdyne" tenant. A user can also be assigned multiple roles in the same tenant. " (http://docs.openstack.org/folsom/openstack-compute/admin/content/keystone-concepts.html#keystone-user-management).
How is it that blueprint is needed to capture the idea that the dashboard should be able to manage multiple roles per project?
The Compute documentation (http:// www.openstack. org/software/ openstack- compute/) clearly states "Dashboard with fully integrated support for self-service provisioning".
It also states that multiple roles are allowed per project. "A user can be assigned different roles in different tenants: for example, Alice may also have the "admin" role in the "Cyberdyne" tenant. A user can also be assigned multiple roles in the same tenant. " (http:// docs.openstack. org/folsom/ openstack- compute/ admin/content/ keystone- concepts. html#keystone- user-management).
How is it that blueprint is needed to capture the idea that the dashboard should be able to manage multiple roles per project?