Bug 1332214 - Fine-grained access to cartridges
Summary: Fine-grained access to cartridges
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-02 14:11 UTC by dwilloug
Modified: 2016-05-02 14:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-02 14:39:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description dwilloug 2016-05-02 14:11:42 UTC
1. Proposed title of this feature request  

Fine-grained access to cartridges.
  
  
2. Who is the customer behind the request?  
Account: name and acct # <- please include both  

FedC (I'll have to get the number later)

  
TAM customer: no/yes  
SRM customer: no/yes  
Strategic: no/yes  
  
3. What is the nature and description of the request?  

The customer would like to ability to limit which teams have access to specific cartridges.
  

4. Why does the customer need this? (List the business requirements here)  

Most closely aligns with their security model.

  
5. How would the customer like to achieve this? (List the functional requirements here)  

Add teams to a cartridge or have all teams assigned to all cartridges with the options to remove teams from cartridges.
  
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
  
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
  
I could not find one.

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  

No
  
9. Is the sales team involved in this request and do they have any additional input?  
  
They are not involved.

10. List any affected packages or components.  
  
11. Would the customer be able to assist in testing this functionality if implemented?  

Yes


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