Scaleio initiator throws errors when ScaleIO sdc is not installed

[Rajini Karthik]

Calls to the binary drv_cfg are hardcoded in os-brick scaleio initiator. This causes the Scaleio initiator to throws errors when ScaleIO SDC is not installed

drv_cfg executable is already open source, could, therefore, be added to os-brick itself, instead of making it an external dependency.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/687848

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/687848
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=2d694361fe66736c59ca96a2a54c368638445de6
Submitter: Zuul
Branch: master

commit 2d694361fe66736c59ca96a2a54c368638445de6
Author: Ivan Pchelintsev <email address hidden>
Date: Thu Oct 10 13:16:39 2019 +0300

    Remove VxFlexOS connector external dependencies

    The OpenStack os-brick library uses hardcoded paths to binary files to
    interact with the VxFlexOS SDC. This leads to problems when using
    containerized OpenStack (Kolla & Red Hat). Due to the fact that VxFlexOS
    SDC binary files has to be used inside containers (nova, cinder, etc.)
    the overcloud deployment must be performed in 3 stages:
      1) deploy overcloud without additional volume mounts
      2) install the VxFlexOS client on the controller and compute nodes
      3) update overcloud with additional volume mounts

    Using these changes overcloud can be deployed without update step after
    initial deployment since os-brick does not have external dependencies
    and uses python built-in libraries. The scini device through which the
    VxFlexOS client interacts is presented in the containers by default
    because /dev directory from the host is mounted in all containers.

    Change-Id: Ifc4dee0a51bafd6aa9865ec66c46c10087daa667
    Closes-Bug: #1846483

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/train
Review: https://review.opendev.org/691931

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/691937

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/691931
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=6a7b7a3a789ebaf4fca1a5febfc700e5be93b103
Submitter: Zuul
Branch: stable/train

commit 6a7b7a3a789ebaf4fca1a5febfc700e5be93b103
Author: Ivan Pchelintsev <email address hidden>
Date: Thu Oct 10 13:16:39 2019 +0300

    Remove VxFlexOS connector external dependencies

    The OpenStack os-brick library uses hardcoded paths to binary files to
    interact with the VxFlexOS SDC. This leads to problems when using
    containerized OpenStack (Kolla & Red Hat). Due to the fact that VxFlexOS
    SDC binary files has to be used inside containers (nova, cinder, etc.)
    the overcloud deployment must be performed in 3 stages:
      1) deploy overcloud without additional volume mounts
      2) install the VxFlexOS client on the controller and compute nodes
      3) update overcloud with additional volume mounts

    Using these changes overcloud can be deployed without update step after
    initial deployment since os-brick does not have external dependencies
    and uses python built-in libraries. The scini device through which the
    VxFlexOS client interacts is presented in the containers by default
    because /dev directory from the host is mounted in all containers.

    Change-Id: Ifc4dee0a51bafd6aa9865ec66c46c10087daa667
    Closes-Bug: #1846483
    (cherry picked from commit 2d694361fe66736c59ca96a2a54c368638445de6)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/691937
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=5de1afe883f9d38a6d55cb3b54b6761850edcb01
Submitter: Zuul
Branch: stable/stein

commit 5de1afe883f9d38a6d55cb3b54b6761850edcb01
Author: Ivan Pchelintsev <email address hidden>
Date: Thu Oct 10 13:16:39 2019 +0300

    Remove VxFlexOS connector external dependencies

    The OpenStack os-brick library uses hardcoded paths to binary files to
    interact with the VxFlexOS SDC. This leads to problems when using
    containerized OpenStack (Kolla & Red Hat). Due to the fact that VxFlexOS
    SDC binary files has to be used inside containers (nova, cinder, etc.)
    the overcloud deployment must be performed in 3 stages:
      1) deploy overcloud without additional volume mounts
      2) install the VxFlexOS client on the controller and compute nodes
      3) update overcloud with additional volume mounts

    Using these changes overcloud can be deployed without update step after
    initial deployment since os-brick does not have external dependencies
    and uses python built-in libraries. The scini device through which the
    VxFlexOS client interacts is presented in the containers by default
    because /dev directory from the host is mounted in all containers.

    Change-Id: Ifc4dee0a51bafd6aa9865ec66c46c10087daa667
    Closes-Bug: #1846483
    (cherry picked from commit 2d694361fe66736c59ca96a2a54c368638445de6)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/os-brick 2.11.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/os-brick 2.10.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cinder 15.0.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/os-brick 2.8.3 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cinder 14.0.3 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cinder 16.0.0.0b1 development milestone.