Bug 984625 - RFE: cannot create a volume under a specific tenant using the keystone default admin user
Summary: RFE: cannot create a volume under a specific tenant using the keystone defaul...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Eric Harney
QA Contact: Dafna Ron
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-15 14:54 UTC by Dafna Ron
Modified: 2016-04-27 00:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Allow admin to create volumes owned by specified tenant Reason: Result (if any):
Clone Of:
Environment:
Last Closed: 2013-12-18 07:51:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1262597 0 None None None Never

Description Dafna Ron 2013-07-15 14:54:07 UTC
Description of problem:

I wanted to create a volume for a different tenant by logging in with the keystone admin user and we do not have a --tenant tag in create 

I think that since admin user can create a tenanat, a user and assign permissions there is no reason why the same user cannot create an object and assign it to a specific tenant. 

Version-Release number of selected component (if applicable):

openstack-cinder-2013.1.2-3.el6ost.noarch

How reproducible:

100%

Steps to Reproduce:
1. create a volume using admin user
2. 
3.

Actual results:

the volume is created only under the admin tenant and we have no way of creating a volume for a specific tenant using the admin user. 

Expected results:

we should be able to create a volume for a tenant

Additional info:

Comment 1 Eric Harney 2013-09-17 18:30:51 UTC
Are there any OpenStack operations that behave this way?  Creating VMs for tenants, creating images for tenants, etc.?

Comment 2 Dafna Ron 2013-11-21 15:53:11 UTC
well, we can for images since glance help image-create shows: 
 --owner <TENANT_ID>   Tenant who should own image.

Instances run under a specific zone and I think that since we run them from a specific image that they will automatically be assigned to a tenant. 

since volume is an object we can attach or boot to an instance I think that we should be able to create it with --owner

Comment 3 Eric Harney 2013-12-10 20:15:23 UTC
Havana / RHOS 4 now allows transfer of volumes from one owner to another, which I think enables the desired use case here:  admin creates a volume, initiates a volume transfer, provides tenant/user with the credentials needed to accept that transfer.

I would suggest that any further requests around this be handled upstream rather than here as I don't think there is a strong argument for adding this feature in the near future with transfer present in Havana.

Comment 4 Ayal Baron 2013-12-18 07:51:36 UTC
Haim / Dafna, please file upstream.

Comment 5 Summer Long 2014-07-23 04:20:33 UTC
Eric, since nothing was done, have changed the requires_doc_text to -. Unless you think it should be marked as a 'Known Issue' and the doc text gives your workaround?

Comment 6 Eric Harney 2014-09-25 16:20:20 UTC
Agree w/ requires_doc_text- .


Note You need to log in before you can comment on or make changes to this bug.