| Summary: | Unable to define a 'system administrator' user for a zone | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Steve Reichard <sreichar> | ||||
| Component: | aeolus-conductor | Assignee: | Dave Johnson <dajohnso> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Dave Johnson <dajohnso> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 1.0.0 | CC: | akarol, cpelland, deltacloud-maint, hbrock, rlandy, scollier, ssachdev, sseago | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-12-13 19:49:50 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Steve Reichard
2012-02-22 19:27:39 UTC
So a few comments here: 1) images belong to the cloud, and there will be a "Cloud Image Administrator" role that can upload/build/push images and manage catalogs within the cloud. 2) at the Zone level, it sounds like we need a "Zone Application Blueprint Administrator" that can manage catalogs/app blueprints within the zone 3) Adding provider accounts to the zone will be part of "Cloud Administrator" The assigned Cloud Administrator will also need "Provider Account User" rights to add a given provider account. The Cloud admin will not need any specific rights on the Provider itse.f 4) Regarding Provider Owner and User roles -- this relates to a discussion that Jay and I had -- really "Owner" and "Administrator" grant the same level of rights, but there are subtle differences in implication around numbers of users, etc. basically for Provider Accounts, Instances, Applications we'll keep Owner, but for Zones, Clouds, Providers, we should use Administrator. In any case, the rights conferred are the same -- edit/view/use/delete/etc. Scott, we'll wait for the roles docs you're working on to make a decision on this bug one way or another. The fix for 788148 should include everything needed here. Should this be considered a duplicate? This BZ is still marked as 'NEEDINFO' so checking in on what the final decision is ...
In the mean time,
Tested rpms:
>> rpm -qa |grep aeolus
aeolus-configure-2.8.7-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.7.2-1.el6cf.noarch
aeolus-conductor-0.13.14-1.el6cf.noarch
aeolus-conductor-daemons-0.13.14-1.el6cf.noarch
aeolus-conductor-doc-0.13.14-1.el6cf.noarch
aeolus-all-0.13.14-1.el6cf.noarch
I can see that Zone specific roles have been added.
- As admin user, I could assign another user as a Cloud Resource Zone Application Blueprint Administrator. I could then ...
- Log in as that user
- Create a new Application Blueprint and save it
Considering the above results and the fact thet BZ-788148 is closed ... can we verify this BZ?
Created attachment 618089 [details]
Cloud Resource Zone Blueprint Administrator
I think this is sorted now... Good 2 go with the following rpms: aeolus-conductor-0.13.24-1.el6cf.noarch aeolus-conductor-daemons-0.13.24-1.el6cf.noarch aeolus-conductor-doc-0.13.24-1.el6cf.noarch |