3. What is the nature and description of the request?
	Adding custom tags to dynamically created AWS EBS volume. (beside kubernetes.io/created-for/pvc/namespace and kubernetes.io/created-for/pvc/name) 

4. Why does the customer need this? (List the business requirements here) 
	Security policies and billing component relay on tag existence and tag value. 

5. How would the customer like to achieve this? (List the functional requirements here)
	On project/namespace level (OSE admin) and on PVC level (OSE end user) would add annotations (labels or some other metadata) that would be propagated to AWS EBS volume.
    
6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 
	Testing should  be straightforward:
   
	1.	Namespace level:
		a.	OSE admin add annotation to namespace
		b.	OSE end user create pvc
		c.	OSE admin on AWS  check is newly created EBS volume tagged properly
	2	PVC level
		a.	OSE end user create pvc with annotation
		b.	OSE admin on AWS  check is newly created EBS volume tagged properly

7. Is there already an existing RFE upstream or in Red Hat bugzilla? 
	N/A 
8. Does the customer have any specific timeline dependencies?
	We would need this until July 2016.
9. Is the sales team involved in this request and do they have any additional input?
	No
10. List any affected packages or components.
	OSE integration part with AWS EBS (or some other volume provisioner)
11. Would the customer be able to assist in testing this functionality if implemented?
	Yes