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

Bug 1676868

Summary:	[Docs][RFE][nth-4.4][TP] Add missing cinderlib clients drivers for different backend storages
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Avihai <aefrat>
Component:	Documentation	Assignee:	Eli Marcus <emarcus>
Status:	CLOSED DUPLICATE	QA Contact:	rhev-docs <rhev-docs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4.0	CC:	emarcus, lsurette, sbonazzo, sgoodman, srevivo, tnisan
Target Milestone:	ovirt-4.4.1	Keywords:	Documentation, FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-29 15:35:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Docs	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1647196

Description Avihai 2019-02-13 12:53:15 UTC

Description of problem:
Currently, we need to install backend storage client drivers manually on ovirt-engine per each backend storage, without it, clinderLib/managed block feature will not work.

As decided in Bug 1673041 this will be the user's responsibility as in Open stack so we must add this in the documentation about what drivers to add in the engine host.


For full driver list:
https://docs.openstack.org/ocata/config-reference/block-storage/volume-drivers.html


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

How reproducible:
100%

Steps to Reproduce:
1.Check if the cinderlib clients drivers for different backend storages:
> pip show <driver_name> 
> pip show krest
> pip show python-3parclient


Actual results:

Expected results:
We should document that for cinderLib to work for specific storage backends specific drivers needs to be installed in the ovirt-engine host by the user first.

For full driver list:
https://docs.openstack.org/ocata/config-reference/block-storage/volume-drivers.html


Additional info:

Comment 1 Steve Goodman 2019-05-21 14:10:58 UTC

(In reply to Avihai from comment #0)

> As decided in Bug 1673041 this will be the user's responsibility as in Open
> stack so we must add this in the documentation about what drivers to add in
> the engine host.

Is this already documented in the Open Stack documentation so we can just point to it?

 > For full driver list:
> https://docs.openstack.org/ocata/config-reference/block-storage/volume-
> drivers.html

So this is what I understand that the user needs to do:

1. Identify the driver for their hardware using the list at [1]
2. Click the link for their hardware in [1] to see detailed requirements and instructions for each driver.

> We should document that for cinderLib to work for specific storage backends
> specific drivers needs to be installed in the ovirt-engine host by the user
> first.

"ovirt-engine host" is not clear to me. Do the drivers need to be installed in a host, or on the RHVM machine?
 
[1] https://docs.openstack.org/ocata/config-reference/block-storage/volume-drivers.html.

Comment 2 Avihai 2019-05-21 14:27:54 UTC

(In reply to Steve Goodman from comment #1)
> (In reply to Avihai from comment #0)
> 
> > As decided in Bug 1673041 this will be the user's responsibility as in Open
> > stack so we must add this in the documentation about what drivers to add in
> > the engine host.
> 
> Is this already documented in the Open Stack documentation so we can just
> point to it?
Yes we can.

>  > For full driver list:
> > https://docs.openstack.org/ocata/config-reference/block-storage/volume-
> > drivers.html
> 
> So this is what I understand that the user needs to do:
> 
> 1. Identify the driver for their hardware using the list at [1]
> 2. Click the link for their hardware in [1] to see detailed requirements and
> instructions for each driver.
Correct.

> > We should document that for cinderLib to work for specific storage backends
> > specific drivers needs to be installed in the ovirt-engine host by the user
> > first.

Correct

> "ovirt-engine host" is not clear to me. Do the drivers need to be installed
> in a host, or on the RHVM machine?
RHVM engine machine.

In more details:
cinderlib client in RHV is using these drivers to communicate with the backend storage which has a cinderlib server.

> [1]
> https://docs.openstack.org/ocata/config-reference/block-storage/volume-
> drivers.html.