[IBM Storwize] Optimize SSH calls in create replicated volume

[nikeshkm]

In create gmcv volume flow, we call create_vdisk four times

first two create_vdisk calls -> is_volume_type_dr_pools -> lsmdiskgrp is not called since pool information was there in stats

last two create_vdisk calls -> is_volume_type_dr_pools - lsmdiskgrp is called (Total 2 lsmdiskgrp ) since pool information was not there in stats

lsmdiskgrp call can be reduced if pool information is present.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/cinder/+/848418

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/cinder/+/848418
Committed: https://opendev.org/openstack/cinder/commit/c34ba3c9756c78f6a3b7361c30de4f0eb766dbaf
Submitter: "Zuul (22348)"
Branch: master

commit c34ba3c9756c78f6a3b7361c30de4f0eb766dbaf
Author: sreerammounika <email address hidden>
Date: Mon Jul 4 08:24:13 2022 +0000

    [SVf] Optimize lsmdiskgrp calls in creation of replicated volumes

    [Spectrum Virtualize family] During creation of replicated volumes,
    lsmdiskgrp calls are made at L919 in storwize_svc_common.py file as
    the secondary pools information is not available in stats.

    Hence, Optimized the lsmdiskgrp SSH calls to reduce the computational
    time by storing the secondary pools information in stats.

    Closes-Bug: #1978290
    Change-Id: Iea7a7b7d7ce226b3c29aba9641b052ee7fe8614f

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cinder 22.0.0.0rc1 release candidate.