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

Bug 1185609

Summary:	[RFE] - easy installation for optimizer
Product:	[Retired] ovirt-optimizer	Reporter:	Shira Maximov <mshira>
Component:	RFEs	Assignee:	Martin Sivák <msivak>
Status:	CLOSED DEFERRED	QA Contact:	Shira Maximov <mshira>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	bugs, dfediuck, mgoldboi, msivak, pstehlik, sbonazzo
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	dfediuck: ovirt-4.2? sherold: Triaged+ ylavi: planning_ack+ dfediuck: devel_ack? pstehlik: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-06 18:08:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Shira Maximov 2015-01-25 08:59:07 UTC

Description of problem:
The installation of the opta planner quite complicated,
There are lots of files to configure.
The installation should be more comfortable and should be a single command that asks the user questions regarding the installation.

For example the installation of the ovirt engine, you only run the command: engine-setup and and it asks the user all the necessary questions.
the questions for the opta planner can be:
what is your engine ip?  ? do you want to allow port 8080 to allow the application communication? enter the credentials for the REST API..

Comment 1 Doron Fediuck 2015-02-12 09:04:17 UTC

We need to wait for the underlying project (BRMS) to ship before we can
do any changes in the setup procedures.

Comment 2 Yaniv Kaul 2015-11-26 14:17:56 UTC

(In reply to Doron Fediuck from comment #1)
> We need to wait for the underlying project (BRMS) to ship before we can
> do any changes in the setup procedures.

Doron - where is the bug on BRMS that we can have this bug depend on, as well as push to get it implemented?

Comment 3 Doron Fediuck 2015-11-26 15:43:05 UTC

(In reply to Yaniv Kaul from comment #2)
> (In reply to Doron Fediuck from comment #1)
> > We need to wait for the underlying project (BRMS) to ship before we can
> > do any changes in the setup procedures.
> 
> Doron - where is the bug on BRMS that we can have this bug depend on, as
> well as push to get it implemented?

I'm working on this with Moran and the BRMS team.
Moran, do we have an RFE for OptaPlanner RPM?

Comment 4 Moran Goldboim 2015-12-29 11:08:02 UTC

(In reply to Doron Fediuck from comment #3)
> (In reply to Yaniv Kaul from comment #2)
> > (In reply to Doron Fediuck from comment #1)
> > > We need to wait for the underlying project (BRMS) to ship before we can
> > > do any changes in the setup procedures.
> > 
> > Doron - where is the bug on BRMS that we can have this bug depend on, as
> > well as push to get it implemented?
> 
> I'm working on this with Moran and the BRMS team.
> Moran, do we have an RFE for OptaPlanner RPM?

No RFE I'm aware of, I would continue chasing it after shutdown.

Comment 5 Sandro Bonazzola 2016-08-18 12:24:54 UTC

*** Bug 1367698 has been marked as a duplicate of this bug. ***

Comment 6 Moran Goldboim 2016-08-29 08:43:39 UTC

Martin, 
-what is the size of the installed packages?
-what would be the optimal deployment option we are looking for?
  -on the engine
  -a separate vm
  -a separate container

Comment 7 Sandro Bonazzola 2016-09-16 06:57:24 UTC

Moving to SLA, integration will provide support when needed.

Comment 8 Martin Sivák 2016-11-01 08:44:42 UTC

The optimal deployment is either a separate VM or a container (or a physical host).

The disk space consumed by the yum install using oVirt 4.0.6 RPMs is 297 MiB (including full oVirt JBoss) + additional 135 MiB for the downloaded Optaplanner zip.