Bug 681004

Summary:	only admin can create templates and deploy instances
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Dave Johnson <dajohnso>
Component:	aeolus-conductor	Assignee:	Scott Seago <sseago>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Dave Johnson <dajohnso>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	0.3.1	CC:	cpelland, deltacloud-maint, morazi, whayutin
Target Milestone:	alpha
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-14 15:53:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	644050, 669238, 684278

Description Dave Johnson 2011-02-28 18:38:25 UTC

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.

Comment 1 wes hayutin 2011-03-11 16:58:57 UTC

adding to the ce-beta blocking tracker

Comment 2 wes hayutin 2011-03-16 14:28:56 UTC

*** Bug 683907 has been marked as a duplicate of this bug. ***

Comment 3 wes hayutin 2011-03-16 14:29:13 UTC

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.

Comment 4 wes hayutin 2011-03-17 18:34:01 UTC

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?

Comment 5 Scott Seago 2011-03-18 13:27:14 UTC

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

Comment 6 wes hayutin 2011-06-14 15:53:58 UTC

closing out old bugs that dev has not addressed :(

Comment 7 wes hayutin 2011-12-08 13:51:56 UTC

perm close