3par driver isn't honoring pool

[Walt Boring]

Previous to pool support, the 3PAR driver allowed CPG's to be specified in the extra specs for a volume type, to determine what CPG(Pool) the volume would be created. Now that Kilo supports pools, the pool name is passed into the host entry at create time.

The 3PAR driver isn't honoring the choice of the scheduler, but still using the CPG specified in the extra specs. This can potentially get you in a broken state.

A driver can be reporting CPG A and B as pools, but the volume type could be C. Currently the 3PAR driver will create the volume on Pool C.

3PAR driver needs to deprecate the usage of CPG in volume type extra specs, and honor the scheduler's pool name in the host.

[Mike Perez (thingee)]

I'm assuming this is in progress?

[Kurt Martin (kurt-f-martin)]

This problem also affects volume retype and volume migration, in additonal to the reported create volume

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/165605
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=ef442251f43d0ffea86118dbb6fb5227820c8ef1
Submitter: Jenkins
Branch: master

commit ef442251f43d0ffea86118dbb6fb5227820c8ef1
Author: Walter A. Boring IV <email address hidden>
Date: Wed Mar 18 14:11:45 2015 -0700

    Make the 3PAR drivers honor the pool in create

    Currently, the 3PAR drivers rely on the pool (CPG) existing
    in the extra specs of a volume type. This is the way that the
    3PAR drivers supported the idea of 'pools' prior to Cinder
    itself supporting pools.

    Now, the 3PAR drivers will not use the CPG specified in the
    extra specs of a volume type. The drivers will log a warning
    explaining that CPG is deprecated, and then override the CPG
    setting with the pool name specified by the scheduler in the
    volume['host'] entry. This fixes a few bugs in the 3PAR
    drivers.

    Existing 3PAR deployments will need to update their cinder.conf
    to specify the list of CPGs they want the driver to support as
    pools in the hp3par_cpg=[list of cpgs] entry. hp3par_cpg can be
    a single CPG, or a comma separated list of CPGS.

    The 3PAR best practice guide will be updated for the Kilo release
    explaining how to upgrade from existing deployments and describe
    how best to use CPGS as pools.

    Closes-Bug: #1432876
    DocImpact

    Change-Id: I2c733ff3f13ba309cc07e07331b4945b1981a07a