Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1081703

Summary: [Doc][RFE] Support for Cinder v2
Product: Red Hat OpenStack Reporter: Summer Long <slong>
Component: doc-Administration_User_GuideAssignee: Deepti Navale <dnavale>
Status: CLOSED NOTABUG QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0CC: aortega, ddomingo, dron, iovadia, jpichon, mrunge, rhos-integ, yeylon
Target Milestone: Upstream M3Keywords: Documentation, FutureFeature
Target Release: 5.0 (RHEL 7)   
Hardware: x86_64   
OS: Linux   
URL: https://blueprints.launchpad.net/horizon/+spec/cinder-v2-horizon
Whiteboard: docs-rhos5-ups storage upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Reason: Result (if any):
Story Points: ---
Clone Of: 1035790 Environment:
Last Closed: 2014-07-09 01:01:02 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:
Embargoed:
Bug Depends On: 1035790    
Bug Blocks:    

Description Summer Long 2014-03-27 19:06:39 UTC
+++ This bug was initially created as a clone of Bug #1035790 +++

Description of problem:

cinder endpoint v2 changed the volume names attr to --name instead of --display-name.

when I change the cinder endpoint to v2 and create volumes, horizon crashes when we try to query the volumes

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

python-django-horizon-2013.2-5.el6ost.noarch

How reproducible:

100%

Steps to Reproduce:
Run the following in cli:

1. install openstack with packstack
2. change cinder's endpoint in keystone to v2:

keystone endpoint-create --region RegionOne --service-id 10fd33fdca4f4ca4a2e21c2c786a3495 --publicurl 'http://<ip>:8776/v2/%(tenant_id)s' --adminurl 'http://<ip>:8776/v2/%(tenant_id)s' --internalurl 'http://<ip>:8776/v2/%(tenant_id)s'

delete the old v1 endpoint:

keystone endpoint-delete <endpoint that uses v1>

3. create a volume using v2 API:

OS_VOLUME_API_VERSION=2 cinder create 10 --name <name>

4. log in to horizon -> project -> volumes

Actual results:

Horizon gives an attr error on name

Expected results:

we should be able to query both v1 and v2 attr. 
but if not we need a clear error and not an attr error. 

--- Additional comment from Julie Pichon on 2014-02-12 05:20:39 EST ---

How to test (copied from blueprint's whiteboard in case it gets lost):

In the local settings, set 'volume' in OPENSTACK_API_VERSIONS to 1 or 2 depending on the version you want to test.

OPENSTACK_API_VERSIONS = {
    "volume": 2
}

If your debug levels are set, you should be able to verify that the cinderclient calls are using the appropriate v1 or v2 URL.

Panels of interests:
* Volumes: All the volume actions should still work using either v1 or v2
* Images & Snapshots: Volume snapshots actions should work using v1 and v2
* Instances: Create instance has several options related to volumes and booting from volumes, these should still work and the volumes or volume snapshots displayed correct
* Admin - Volumes: Should display correctly, no changes for volume types which are still expected to work with both versions.

The name display was also generally improved so that the volume id is always shown if the volume doesn't have a name.

Comment 2 Don Domingo 2014-03-28 03:48:55 UTC
Looks like Cinder v2 is already supported, at least as far as the docs are concerned:
    http://docs.openstack.org/user-guide/content/cinder_commands.html
    http://docs.openstack.org/user-guide-admin/content/cinderclient_commands.html

See the documentation on "--os-volume-api-version" on both pages.

I looked at the docs, and there are no current procedures where this option is relevant or even used. I'm not seeing a documentation impact here, at least for Cinder; also, from the original bug (BZ#1035790) it looks like a fix would not have any docs impact at all. 

Setting Julie Pichon as NEEDINFO on this. Julie, is there an actual docs impact on this? Or can I close this NOTABUG?

Comment 4 Julie Pichon 2014-03-28 08:40:15 UTC
The original bug is about Horizon adding support for Cinder v2. Before that, when using Horizon with a Cinder v2 endpoint, Horizon would error on the Volumes page. I described the configuration change to Horizon's local_settings.py in the doc text for the original bug, if one wishes to enable Cinder v2 in the dashboard. I'm not sure if we usually document these (for instance you can use the same setting to work with Keystone v3 since Havana).

With regard to endpoints, I have v1 and v2 explicitly set up in my endpoints URLs as well FWIW. Cinder supports having 2 volume endpoints, of type 'volume' and 'volumev2' respectively. This is a way to make it possible to work with Cinder even with services that don't fully support it (e.g. Horizon until now, and I believe Nova still doesn't support Cinder v2 either). For more details, it probably would be better to ask one of the Cinder folks directly. Thanks!

Comment 5 Don Domingo 2014-03-31 23:34:39 UTC
Reassigning to Deepti Navale to process any dashboard-related docs changes.