Bug 1136726

Summary:	[RFE] Support partial cleanup for dwh
Product:	[oVirt] ovirt-engine-dwh	Reporter:	Shirly Radco <sradco>
Component:	RFEs	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED DUPLICATE	QA Contact:	Gonza <grafuls>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	bugs, didi, ecohen, gklein, iheim, rbalakri, Rhev-m-bugs, sbonazzo, yeylon, ylavi
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	ylavi: ovirt-future? sherold: Triaged+ rule-engine: planning_ack? sradco: devel_ack? rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1169695 (view as bug list)		Environment:
Last Closed:	2015-12-20 12:40:00 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:	1060529
Bug Blocks:	1169695

Description Shirly Radco 2014-09-03 07:22:49 UTC

Allow the user to relocate its dwhd (etl process) to a new host and give the option of using current db.

1. On setup of the new dwh, ask the user if he wants to replace currecnt dwh.

2. If the user accepts and the other dwh process is still running we want to signal it to stop , and address the issue of the cron job so it will not reactivate it again.

3. Also if the user chosen to you current db we need to make sure it will not be cleaned during engine-cleanup on the old host.

Comment 1 Shirly Radco 2015-01-04 11:19:42 UTC

Clarification for Comment #1.

We want to support a flow that a user that wants to relocate its DWH will be able to run partial cleanup, that will allow him to keep current history DB.
And will also remove the uuid from the engine db. 

Then when the user will run engine-setup for the new dwh at the new location he will not be required to answer if he wants to replace the old installation and will be able to use the old history db.

Comment 2 Yedidyah Bar David 2015-12-20 07:29:10 UTC

Can this one be closed as duplicate of bug 1169695?

In the past it was a downstream bug, but was recently changed.

Comment 3 Yaniv Lavi 2015-12-20 12:40:00 UTC


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