Bug 1651907

Summary:	[RFE] foreman-proxy to send SCAP reports with a splay
Product:	Red Hat Satellite	Reporter:	Pavel Moravec <pmoravec>
Component:	SCAP Plugin	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Sanket Jagtap <sjagtap>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	mhulan, oprazak
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-15 20:30:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavel Moravec 2018-11-21 07:29:05 UTC

Description of problem:
OpenSCAP reports are sent by foreman-proxy in a bulk every 30 minutes due to cronjob:

# cat /etc/cron.d/rubygem-smart_proxy_openscap
# Send all collected OpenSCAP reports once every 30 minutes
*/30 * * * * foreman-proxy smart-proxy-openscap-send >> /var/log/foreman-proxy/cron.log
#

It is possible this does not scale well - assume 10+ Capsules with 1k+ Hosts registered, all sending SCAP report (of usual size 250k each) - and Satellite receives the 2.5G of data to parse and process and store within a short interval, synchronously from all Capsules.

We should implement some splay mechanism like puppet or rhsmcertd has.


Version-Release number of selected component (if applicable):
Sat 6.4


How reproducible:
???


Steps to Reproduce:
1. Have more Capsules with many clients registered to each, applying few SCAP policies on each
2. Monitor load on Satellite at */30 times


Actual results:
2. is suspected to have high load


Expected results:
2. The high load should be distributed more evenly


Additional info:

Comment 1 Pavel Moravec 2018-11-21 07:30:08 UTC

(there is no real use case or customer behind this, so far; just a worry we can hit a scalability limitation if not implemented)

Comment 2 Ondřej Pražák 2018-11-21 09:22:00 UTC

Connecting redmine issue http://projects.theforeman.org/issues/22582 from this bug

Comment 3 Bryan Kearney 2019-12-03 16:34:42 UTC

The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 4 Bryan Kearney 2020-01-15 20:30:26 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.