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

Bug 1365427

Summary:	engine-setup asks about scale also on upgrade/restore from 3.6
Product:	[oVirt] ovirt-engine-dwh	Reporter:	Yedidyah Bar David <didi>
Component:	Setup	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.6.0	CC:	bugs, didi, lsvaty, sradco, ylavi
Target Milestone:	ovirt-4.0.5	Flags:	rule-engine: ovirt-4.0.z+ ylavi: planning_ack+ sbonazzo: devel_ack+ lsvaty: testing_ack+
Target Release:	4.0.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: In 4.0, dwh engine-setup plugin prompts the user to choose between 'Full' and 'Basic' scale. If dwh is on the same machine as the engine, it defaults to 'Basic'. In past 4.0 releases, it always asked this question on upgrade from 3.6. Consequence: If dwh was already set up in 3.6, and used the default configuration, which is equivalent to 4.0's 'Full', and the user didn't pay attention to this question and pressed Enter, configuration was changed to 'Basic', potentially removing most of the history data collected. Fix: Now this question is asked, and scale is configured, only if this is a new dwh database setup, and not if the database already exists, e.g. not if it is an upgrade. Result: On upgrade, this question is not asked, configuration is not changed, and history data is not removed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-18 07:38:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1379120

Description Yedidyah Bar David 2016-08-09 09:00:20 UTC

Description of problem:

In bug 1328805 we added a question about scale.

We ask this question also during upgrade from 3.6, including if restoring a 3.6 backup on a 4.0 system.

Not sure about the perfect solution. One might even claim it's not a bug.

In 3.6 we didn't have this question, so do not know the answer. Current 'Full' was the default then, and changing it required manually editing config files.

Perhaps changing the prompt text is enough.

A "full" (but somewhat hacky) solution can be to check current conf, and ask if different from default. Note that in 4.0 the default depends on whether dwh is with the engine on same machine - "Basic" if yes, "Full" if different machines.

A related question (might be worth another bug) is that we always rewrite the configuration on upgrade. So a user manually changing the conf after running engine-setup will have the changes overwritten by a next upgrade. This isn't specific to the dwh scale params, it applies to many other questions.

Comment 1 Yaniv Lavi 2016-08-11 08:36:12 UTC

We should keep it as 'full' in upgrades that had DWH previously installed in 3.6 or even better ask and have 'full' as default option.
In any case in fresh install or upgrade without DWH, we need to ask.

Comment 2 Yedidyah Bar David 2016-09-11 13:08:00 UTC

Thinking about this again, I think it's enough if we only ask this question, and configure scale, if we are setting up a new database. On any setup with existing database (upgrade, migration, etc.) we do nothing. dwhd will then use its defaults or whatever manual configuration the admin did.

Comment 3 Shirly Radco 2016-09-11 19:28:31 UTC

But when do we set the sampling interval to 15 instead of 60?
Is this done in a separate step?

Comment 4 Yedidyah Bar David 2016-09-12 06:31:54 UTC

(In reply to Shirly Radco from comment #3)
> But when do we set the sampling interval to 15 instead of 60?
> Is this done in a separate step?

When? On upgrade? Never.

On clean setup - same as today.

Do we have to do anything on upgrade?

Comment 5 Shirly Radco 2016-09-12 17:47:51 UTC

Yes. We should update the sampling interval to 15 seconds same as in clean setup.
This is for better dashboards accuracy.

Comment 6 Yedidyah Bar David 2016-09-13 05:43:34 UTC

(In reply to Shirly Radco from comment #5)
> Yes. We should update the sampling interval to 15 seconds same as in clean
> setup.
> This is for better dashboards accuracy.

Which parameter exactly?

Comment 7 Shirly Radco 2016-09-13 08:53:44 UTC

Please disregard. It is unrelated and already addressed it.

Comment 8 Lukas Svaty 2016-10-18 15:54:17 UTC

verified in ovirt-engine-dwh-setup-4.0.2-1.el7ev.noarch