In the old UI, self service users were able to deploy instances from templates that the admin user had created. It now looks like in the new UI, templates are strictly private per user. I assume this is expected but when I create a self service user (or login with a admin created user) they don't have the permission to create their own templates let alone deploy instances from another user's templates. As it stands, it looks like only the admin user can create templates and deploy instances. It is our understanding that non-admin users should at a minimum be able deploy their own instances.
adding to the ce-beta blocking tracker
*** Bug 683907 has been marked as a duplicate of this bug. ***
Description of problem: recreate: As admin 1. create a template 2. create proper hwp 3. create a non-admin 0r self service user test01/password log out/log in as the test01 4. launch an instance 5. notice the "pool" combo box is not populated. The default pool is required for launch, and the user is not able to launch as a result.
We need an update on this function describing what proper function should look like for 1.0 1. can users start instances? 2. can users create templates? 3. are there public/private templates?
The first cut of this (until we get a permissions UI) will be as follows: We need to change the infrastructure around assigning default permissions to self-service users to grant them template creation permissions and site-wide template view/use permissions in addition to the current permissions on the default pool. The end result of this will be: 1) all users can create templates 2) all users can use all templates to start instances (the default permissions will grant site-wide template access, making all templates essentially public) 3) all users can start instances in the default pool
closing out old bugs that dev has not addressed :(
perm close