Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 537479

Summary:	[RFE] Rate-limit the amount of bytes upload-able to lab controller/scheduler
Product:	[Retired] Beaker	Reporter:	Kevin Baker <kbaker>
Component:	lab controller	Assignee:	beaker-dev-list
Status:	CLOSED NOTABUG	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	0.5	CC:	bpeck, dcallagh, ineilsen, kbaker, mcsontos, rmancy, tools-bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	SimpleHarness
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-25 23:53:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kevin Baker 2009-11-13 19:33:47 UTC

Description of problem:

Potential issue with throughput when having labs across the WAN all pushing logs back to a central scheduler.

There should be knobs/controls on the test harness or lab controller to limit how much data it will accept to push up to the scheduler.

<fantasy-not-sure-if-useful-idea>
if it was useful then a test writer could indicate which part of the logs it was interested in. ala tail or head. 
</fantasy-not-sure-if-useful-idea>

Comment 1 Marian Csontos 2010-02-24 10:18:34 UTC

At the moment Harness is serializing all requests to LC, thus if LC has high latency, it will slow down. If this is not enough for communication between LM and LC, we should use traffic shaping on LC.

Test writer can indicate which part of log is interesting: just has to use head or tail in his (or her) the tests.

Comment 2 Nick Coghlan 2012-10-17 04:39:08 UTC

Bulk reassignment of issues as Bill has moved to another team.

Comment 4 Nick Coghlan 2014-06-25 00:23:24 UTC

Dan, can we close this one based on the HTTP upload size limiting going into 0.17.1?

The RFE also seems to predate logs remaining local to each lab.

Comment 5 Dan Callaghan 2014-06-25 23:53:08 UTC

Yes, the original concern about sending all logs from LC -> server over (potentially) slow WAN links is no longer relevant, we now store all logs within the lab until beaker-transfer comes along after the fact to move them.