Bug 1376007

Summary:	Allow installing proliant tools from an OS package
Product:	Red Hat OpenStack	Reporter:	Benjamin Schmaus <bschmaus>
Component:	diskimage-builder	Assignee:	Ben Nemec <bnemec>
Status:	CLOSED CANTFIX	QA Contact:	Arik Chernetsky <achernet>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	9.0 (Mitaka)	CC:	mburns, rhel-osp-director-maint
Target Milestone:	---	Keywords:	Tracking, Upstream
Target Release:	10.0 (Newton)
Hardware:	x86_64
OS:	Linux
URL:	https://review.openstack.org/#/c/344214/
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-14 13:51:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Benjamin Schmaus 2016-09-14 12:48:19 UTC

Description of problem:

The Python proliant-tools library is packaged as an RPM, but it depends on a set of closed-source CLI tools. These CLI tools are available as an RPM, but not through normal channels, so must be installed by fetching the RPM from a URL. This patch 

- splits the proliant-tools element into proliant-lib (the Python library) and proliant-utilities (the CLI tools) 
- adds a package installation method for proliant-lib 


Version-Release number of selected component (if applicable):
OSP9

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: https://review.openstack.org/#/c/344214/

Comment 2 Mike Burns 2016-09-14 13:51:37 UTC

(In reply to Benjamin Schmaus from comment #0)
> Description of problem:
> 
> The Python proliant-tools library is packaged as an RPM, but it depends on a
> set of closed-source CLI tools. These CLI tools are available as an RPM, but
> not through normal channels, so must be installed by fetching the RPM from a
> URL. 

The fact that they're closed source means that this is something that Red Hat cannot ship or support or include in our images.  Upstream is welcome to add this element, but if it gets included in the default elements for the ipa ramdisk, we have to actually patch it out downstream.