Bug 1514550

Summary: [RFE] seed the manageiq-client python binding in the appliance
Product: Red Hat CloudForms Management Engine Reporter: John Hardy <jhardy>
Component: ApplianceAssignee: Gregg Tanzillo <gtanzill>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: high Docs Contact:
Priority: high    
Version: 5.9.0CC: abellott, bdunne, cpelland, jhardy, jrafanie, obarenbo, simaishi, smallamp
Target Milestone: GAKeywords: FutureFeature
Target Release: cfme-future   
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: 2018-08-09 22:06:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:

Description John Hardy 2017-11-17 18:36:02 UTC
The appliance does not currently include the python binding library manageiq-client.

please seed it for shipping.

thanks

Comment 2 Joe Rafaniello 2017-12-08 20:27:48 UTC
Do you mean https://github.com/ManageIQ/manageiq-api-client-python ?

If so, is GPL2 ok?
Is it correct in assuming that this would need to become an rpm?  Is this already done?
If this is installed as an rpm, are there other steps required?

If you've done this manually already, please provide the steps you followed and more details, thank you!

Comment 3 Gregg Tanzillo 2017-12-12 19:23:12 UTC
John, ping - need info from you since this is flagged as a blocker. Thanks.

Comment 4 Brandon Dunne 2018-08-09 22:06:03 UTC
Dependency problems: (RPMs, Python packages, Ruby Gems, Ansible modules, etc.)

Several of us on the platform team met recently to discuss dependency problems and came up with the following decisions:
- The appliance will carry dependencies for the application and any necessary debugging tools
- The application itself will declare all of its dependencies as it has in the past
- Application plugins will declare their dependencies in a way that the application / appliance build code can aggregate and install them
- Customer dependencies will need to be installed and maintained by customers since it is impossible for us to maintain and upgrade that list of dependencies.  We can not guarantee that any changes to these dependencies will not break scripts that are not maintained by the engineering team.

*** This bug has been marked as a duplicate of bug 1573658 ***

Comment 5 Red Hat Bugzilla 2023-09-14 04:12:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days