default cinder.conf should follow API deprecation warning
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
Sean McGinnis |
Bug Description
The default version of Cinder's cinder.conf delivered in the Juno 2014.2.1 includes the following two entries (and corresponding configuration entries in cinder/
# DEPRECATED: Deploy v1 of the Cinder API. (boolean value)
#enable_v1_api=true
# Deploy v2 of the Cinder API. (boolean value)
#enable_v2_api=true
As a result, deploying with the stock cinder.conf results in the following WARNING to be logged
WARNING cinder.api [-] The v1 api is deprecated and will be removed after the Juno release. You should set enable_v1_api=false and enable_v2_api=true in your cinder.conf file.
To avoid confusion and further bug reports, switching the value of enable_v1_api default to false for the remaining Juno releases should be considered.
Changed in cinder: | |
assignee: | nobody → Mike Perez (thingee) |
status: | New → In Progress |
Changed in cinder: | |
importance: | Undecided → Low |
There is a review is progress for this: https:/ /review. openstack. org/#/c/ 145703/