Tenant-level access control over glance images
Summary
=======
If openstack administrator wants to make an image public for only one project, currently there is no solution other than making it completely public. So in this case all of the projects(tenants) have full access to the image. Like flavors, having tenant-level access control over the glance images is an awesome feature.
Motivation
========
Will be written...
Description
=========
Will be written...
UX
===
Will be written...
Testing
======
Will be written...
Outside Dependencies
==================
Will be written...
Requirements Update Required
=======
Will be written...
Doc Impact
=========
Will be written...
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- hossein zabolzadeh
- Direction:
- Needs approval
- Assignee:
- hossein zabolzadeh
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Lin Hua Cheng
Related branches
Related bugs
Sprints
Whiteboard
[Lin Hua Cheng] Tuesday September 15 2015:
I am curious about this blueprint, we might have a similar use case when an image is created in one project, and then the user wants to share the other images to other projects owner by another users.
[Zabolzadeh] Tuesday September 15 2015:
Yes, exactly. Like flavors, we can have sharing mechanism between different projects, I mean tenant-level access control for images.
[Justin Pomeroy] Thursday September 17th 2015:
This sounds very similar to this other blueprint that seems to be well underway. Is this different?
https:/
[Zabolzadeh] Friday September 18:
@Justin,
Yes, the same, But why that was not implemented, and remained incomplete?
I am interested to implement it.
[Lin Hua Cheng] Thursday September 17th 2015:
I suggest closing this BP as duplicate, reach out to Gerome and perhaps you guys could collaborate to move the patch faster: https:/
[Lin Hua Cheng] Tueday September 22th 2015:
Assign the BP to Zabolzadeh https:/
