Bug 1291196

Summary: [RFE] - Extend smart proxy affinity to include the host
Product: Red Hat CloudForms Management Engine Reporter: Prasad Mukhedkar <pmukhedk>
Component: SmartState AnalysisAssignee: John Hardy <jhardy>
Status: CLOSED WONTFIX QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.0.1CC: hkataria, jhardy, jocarter, mpovolny, obarenbo
Target Milestone: GAKeywords: FutureFeature
Target Release: cfme-future   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-11 18:09:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Feature
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Prasad Mukhedkar 2015-12-14 09:33:07 UTC
Description of problem:

Host scans are currently a zone based tasks and is not controlled by the smart proxy affinity worker or configuration. The configuration given in the 
zone settings 'smart proxy affinity' is for scanning datastores and virtual machines. 

I would like the smart proxy affinity to be extended to include the host, 
instead of being limited to the vms running on it.

ie. hypervisor 1 is tagged as being managed by appliance 1
All VMs on hypervisor 1 will be smart stated by appliance1
hypervisors1 is also smartstated by appliance1

Current it is random which appliance smart states the hypervisors.
With our network topology this is causing issues.
We have two options at the moment
- suffer a large number of smart state failures on hypervisors
- create rules to allow traffic from the red zone network back to green zone network (against our network policy)