VMAX driver doc does not specify required licenses for cloning

Bug #1580795 reported by Carl Pecinovsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
Low
Alexandra Settle

Bug Description

The mitaka driver info location is: http://docs.openstack.org/mitaka/config-reference/block-storage/drivers/emc-vmax-driver.html

There is a System Requirements section that lists some software components and levels; however, I believe the required VMAX electronic licenses need to be listed as well.

Driver was tried out on a VMAX-3. Got this failure:

ERROR.... Bad or unexpected response from the storage volume backend API: Error Create Cloned Volume: volume-myVM-4feee0fe-00000001-boot--5571521d-9bd5 Return code: 1. Error: The feature being requested is not currently licensed.

in: File "/usr/lib/python2.7/site-packages/cinder/volume/drivers/emc/emc_vmax_provision_v3.py", line 274, in create_element_replica

Please document what is needed. Thanks. From my read of EMC docs, it may be the following:

VMAX-2: SYMM_VMAX_TF_CLONE
VMAX-3: Local_Replication_Suite

The VMAX-3 in question already reports the following licenses:

Associator Name 0:
Symm_InventorySoftwareIdentity.InstanceID="SYMMETRIX-+-<array_id>-+-Advanced_Suite-+-5977_691_684"
Associator Name 1:
Symm_InventorySoftwareIdentity.InstanceID="SYMMETRIX-+-<array_id>-+-Remote_Replication_Suite-+-5977_691_684"
Associator Name 2:
Symm_InventorySoftwareIdentity.InstanceID="SYMMETRIX-+-<array_id>-+-VMAX_OS-+-5977_691_684"

Changed in openstack-manuals:
status: New → Confirmed
Changed in openstack-manuals:
importance: Undecided → Low
milestone: none → newton
Changed in openstack-manuals:
assignee: nobody → Kyle Laffoon (kyle-laffoon)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (master)

Fix proposed to branch: master
Review: https://review.openstack.org/322969

Changed in openstack-manuals:
assignee: Kyle Laffoon (kyle-laffoon) → Helen Walsh (walshh2)
status: Confirmed → In Progress
Revision history for this message
Alexandra Settle (alexandra-settle) wrote :

Hi Helen,

Please note that this was previously being worked on by Kyle Laffoon as a training exercise.
Thank you for your patch, I see no current issues with it - please see my +2.

Please however contact the original assignee in future before taking the bug without notification.

Thanks,

Alex

Revision history for this message
Helen Walsh (walshh2) wrote :

Thanks Alex,
I would like the bug submitter to have a look over it before it gets merged. Would that be possible?

Revision history for this message
Carl Pecinovsky (csky) wrote :

Please see my comment on the review

Changed in openstack-manuals:
assignee: Helen Walsh (walshh2) → Alexandra Settle (alexandra-settle)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/322969
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=a998507816bf3bf087bb9b1e1a9fd4b10ba175f5
Submitter: Jenkins
Branch: master

commit a998507816bf3bf087bb9b1e1a9fd4b10ba175f5
Author: Helen Walsh <email address hidden>
Date: Mon May 30 20:23:12 2016 +0100

    VMAX Driver - Documentation on snapshot licensing

    Instructions on how to get appropriate licenses for
    snapshots for VMAX2 and VMAX3.

    Change-Id: I73168c59499ff4b023cb029b828eaf3c28c630cf
    Closes-Bug: #1580795

Changed in openstack-manuals:
status: In Progress → Fix Released
Revision history for this message
Carl Pecinovsky (csky) wrote :

This was originally a 'finding' against Mitaka. Hopefully the backport there is coming?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-manuals 15.0.0

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.