Bug 1096699

Summary: [RFE] Create Test Method for "set extra specs API of volume-type" for Cinder
Product: [Retired] Red Hat OpenStack Certification Program Reporter: Chandan Kumar <chkumar>
Component: rhosctsAssignee: Chandan Kumar <chkumar>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.0CC: rdas, rreddy, swgoswam
Target Milestone: RCKeywords: FutureFeature
Target Release: 5.0   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-14 13:34:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1094385, 1125278, 1126562, 1132550    
Bug Blocks:    

Description Chandan Kumar 2014-05-12 09:22:04 UTC
Description of problem:

Implement a test method for setting extra specs to a volume type by using set extra specs api for cinder for RHELOSP 5.0

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


How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 2 Ramakrishna Reddy Yekulla 2014-05-22 11:27:05 UTC
Yes, @hugo. we will be supporting this. In addition to we will
provide docucemtation for partners who are trying to configure
CTS for multiple volume types. We have added a test case for this 
particular scenario.  

1. https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/3/html/Installation_and_Configuration_Guide/Configuring_for_Multiple_Storage_Backends.html
2. https://wiki.openstack.org/wiki/Cinder-multi-backend
3. http://docs.openstack.org/trunk/config-reference/content/coraid_aoe_driver_configuration.html

Comment 6 errata-xmlrpc 2014-07-14 13:34:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.