New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 774627 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Blocking:
issue 760652



Sign in to add a comment

Allow provision throttling to be selectively enabled

Reported by jrbarnette@chromium.org, Oct 13 2017

Issue description

Currently, the provision throttling feature only supports
enabling/disabling the feature globally.  In order to move
forward with the feature, we need to be able to enable it
on selected devservers only (see  bug 760652 ).

The feature is a devserver feature, and the devserver has no
configuration file, let alone puppet support for selective
distinctions of this sort.  The most likely mechanism for this
is to add a command-line option to the devserver, and then
include or exclude the option through the upstart job, which
is delivered via puppet.

 
Blocking: 760652
Labels: -Pri-1 Pri-2
Owner: jrbarnette@chromium.org
Status: Assigned (was: Untriaged)
We're not addressing  bug 760652 , so this is moot.

Status: WontFix (was: Assigned)

Sign in to add a comment