Bug 1013356

Summary:	rhevm-setup-plugins - new package for rhevm specific plugins
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Alon Bar-Lev <alonbl>
Component:	distribution	Assignee:	Alon Bar-Lev <alonbl>
Status:	CLOSED ERRATA	QA Contact:	Jiri Belka <jbelka>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	acathrow, alonbl, cboyle, eedri, iheim, pstehlik, Rhev-m-bugs, sbonazzo, srevivo, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	is18	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-21 16:59:13 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:
Bug Depends On:	910377, 977295, 1059668
Bug Blocks:

Description Alon Bar-Lev 2013-09-29 14:59:03 UTC

Currently we patch ovirt-engine to introduce downstream specific setup plugins. It would be nice to stop doing so and package all these plugins within their own git repository and package within their own rpm.

Work already been done, question if we can do this for 3.3.

Nothing is really changed by moving code from patch queue to own rpm.

Comment 5 Alon Bar-Lev 2013-10-01 09:11:04 UTC

QA notes:

1. package rhevm-setup-plugins exists.

2. executing engine-setup pulls downstream specific changes, these will be available at:

 /usr/share/ovirt-egnine/setup/plugins/ovirt-engine-setup/distro-rhel

Comment 6 Jiri Belka 2013-10-30 12:41:41 UTC

ok, is20.1

Comment 7 Charlie 2013-12-06 04:45:05 UTC

Does this need doc text? If so what was done?

Thanks

Comment 8 Alon Bar-Lev 2013-12-08 22:07:06 UTC

(In reply to Charlie from comment #7)
> Does this need doc text? If so what was done?
> 
> Thanks

Not sure what the policy is for these kind of packages.

It is a collection of functionality once was patched into main product.

We split out this functionality so we do not need to patch the main product and can maintain it at its own life cycle.

It currently handles:

1. Upgrade 3.2->3.3 warning and reference to support kb.

2. Copy of downstream only artifacts to iso domain.

3. Post upgrade warning instruction to execute upgrade of these components as well.

4. Configuration of rhevm support plugin.

Comment 9 errata-xmlrpc 2014-01-21 16:59:13 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0081.html