Bug 1601446 - [v2v][RFE] Option for differential inventory refresh
Summary: [v2v][RFE] Option for differential inventory refresh
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: Fabien Dupont
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-16 12:22 UTC by Mor
Modified: 2019-09-18 12:53 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-18 12:53:39 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
evm log (3.40 MB, application/x-gzip)
2018-07-29 08:41 UTC, Mor
no flags Details

Description Mor 2018-07-16 12:22:33 UTC
Description of problem:
There should be an option to run differential refresh inventory from RHV, instead of full refresh inventory, when running V2V migrations.

From what I discovered during V2V tasks analysis, we run refresh inventory per VM, and this task takes relatively long time to complete on a busy and/or big RHV environment, that runs about 4000 VMs and 400 hosts.

Version-Release number of selected component (if applicable):
CFME 5.9.3.4
VMware vSphere 6.5
RHV 4.2.5.1

Comment 2 mlehrer 2018-07-17 13:07:41 UTC
The key take-away here is that for users migrating a plan of multiple vms we expect a much longer total duration for the migration process due to full refresh.  

We wish to avoid any unnecessary extra time in our migration process to keep our migrations within a defined maintenance period.

This rfe was opened to act as a place holder for discussing if its possible to refresh specific rhv assets instead of a full refresh thus reducing the total time of migration from the end users perspective to closer match what would be seen from v2v command line.

Comment 3 Adam Grare 2018-07-20 18:09:44 UTC
RHV should be doing targeted refresh, no config option should be needed.
Can you attach the evm.log containing the refreshes?

Comment 4 Mor 2018-07-29 08:41:41 UTC
Created attachment 1471327 [details]
evm log

Comment 5 Adam Grare 2018-07-30 13:44:02 UTC
It was discovered that the automate handler for V2V was queueing a full refresh when it should be queueing a targeted refresh.  RHV does not require an option to enable targeted refresh because it is the default.


Note You need to log in before you can comment on or make changes to this bug.