Closed Bug 1179134 Opened 10 years ago Closed 10 years ago

Update pipeline tee and edge server configuration for GA

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: whd, Assigned: whd)

Details

(Whiteboard: [unifiedTelemetry] )

The edge and tee servers should be able to scale elastically, based on network or possibly CPU usage. There's not a lot to do here except add those rules. 50 MB/s is the max network throughput for m3.medium, according to my notes.
Assignee: nobody → whd
Priority: -- → P2
Whiteboard: [b5] [unifiedTelemetry]
https://github.com/mozilla-services/svcops/pull/577 has these changes, but needs a review before deployment. The scaling threshold is set to 45MB/s for network throughput, since instance types for both the tee and edge have "moderate" network throughput.
Whiteboard: [b5] [unifiedTelemetry] → [40b7] [unifiedTelemetry] [scaling]
Iteration: --- → 43.1 - Aug 24
Whiteboard: [40b7] [unifiedTelemetry] [scaling] → [unifiedTelemetry]
This is done in the following PRs: https://github.com/mozilla-services/puppet-config/pull/1517 https://github.com/mozilla-services/svcops/pull/653 I will be filing separate bugs for load testing and deployment of these changes.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.