Bug 1395356

Summary: [RFE] Targeted Refresh for Amazon VMs in via vm_object.refresh method
Product: Red Hat CloudForms Management Engine Reporter: Dustin Scott <dscott>
Component: ProvidersAssignee: Julian Cheal <jcheal>
Status: CLOSED ERRATA QA Contact: Matouš Mojžíš <mmojzis>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: brjohnso, cpelland, gblomqui, hhudgeon, jcheal, jfrey, jhardy, lsmola, mkanoor, obarenbo, simaishi, tfitzger
Target Milestone: GAKeywords: FutureFeature
Target Release: 5.9.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 5.9.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 13:08:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: AWS Target Upstream Version:
Embargoed:

Description Dustin Scott 2016-11-15 19:00:13 UTC
-What is the nature and description of the request?
Customer needs the ability to complete a targeted refresh of a VM via a methodology similar to the following:

aws_vm = $evm.vmdb(:vm).first
aws_vm.refresh

The refresh method kicks off a full EMS refresh, rather than a simple update to the individual VM.
  
-Why does the customer need this? (List the business requirements here)
Changing instance attributes (e.g. instance_type) via the aws-sdk does not automatically update the instance.  The instance is stale for an extended period of time, so the customer does not have accurate insight into their infrastructure.
  
-How would the customer like to achieve this? (List the functional requirements here)
Change the .refresh method for MiqAeMethodService::MiqAeServiceManageIQ_Providers_Amazon_CloudManager_Vm class to implement a targeted refresh specific to that VM, rather than a full provider refresh.  A full provider refresh, in very large implementation, will prove to be problematic.
  
-For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
We can run our specific methods (such as changing a flavor), and run the new refresh method and see if it is updated correctly in the VMDB.
  
-Is there already an existing RFE upstream or in Red Hat Bugzilla?
I have not found one.
  
-Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Dec 16
  
-Is the sales team involved in this request and do they have any additional input?
Yes, sales in involved.  Part of next phase of consulting engagement.
  
-List any affected packages or components.
cfme-gemset-5.6.1.2-1.el7cf.x86_64
rh-ruby22-rubygem-redhat_access_cfme-1.0.3-1.el7cf.noarch
cfme-appliance-5.6.1.2-1.el7cf.x86_64
cfme-5.6.1.2-1.el7cf.x86_64

Comment 3 Greg McCullough 2016-11-17 15:52:21 UTC
Automate call the refresh_ems method on the VM which is the proper call.  However, not all providers support a targeted refresh which is what causes the full provider refresh.

Changing the category to Providers.

Comment 9 Julian Cheal 2017-08-21 15:34:57 UTC
Supporting targeted refresh requires condensing the various refresh workers (cloud, network, and storage) into a single refresh worker to avoid running several refreshes in parallel and possibly accidentally duplicating data.

This PR in manageIQ https://github.com/ManageIQ/manageiq/pull/15711 and this one in the Amazon provider https://github.com/ManageIQ/manageiq-providers-amazon/pull/280
achieve this.

Additionally, condensing the refresh workers will reduce the overall memory footprint of an Amazon provider in CFME

Comment 12 Ladislav Smola 2017-09-01 16:07:07 UTC
AWS targeted refresh turned on by default: https://github.com/ManageIQ/manageiq-providers-amazon/pull/290

Comment 13 CFME Bot 2017-09-15 16:02:56 UTC
New commit detected on ManageIQ/manageiq-providers-amazon/master:
https://github.com/ManageIQ/manageiq-providers-amazon/commit/a9723ebb571d7e71046e25a4c31f40271bf9c4d4

commit a9723ebb571d7e71046e25a4c31f40271bf9c4d4
Author:     Ladislav Smola <lsmola>
AuthorDate: Fri Sep 1 13:45:13 2017 +0200
Commit:     Ladislav Smola <lsmola>
CommitDate: Fri Sep 1 13:45:13 2017 +0200

    Turn on graph refresh with targeted refresh as default
    
    Turn on graph refresh with targeted refresh as default
    
    Partially implements:
    https://bugzilla.redhat.com/show_bug.cgi?id=1395356

 config/settings.yml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

Comment 15 Matouš Mojžíš 2018-01-09 15:50:10 UTC
Verified in 5.9.0.15. It's working in 5.9.0, but not in 5.8.3.

Comment 18 errata-xmlrpc 2018-03-01 13:08:18 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.

https://access.redhat.com/errata/RHSA-2018:0380

Comment 19 Red Hat Bugzilla 2023-09-15 00:00:33 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days