Closed
Bug 1145681
Opened 10 years ago
Closed 10 years ago
Investigate ftp proxy in scl3 to reduce zlb load
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Unassigned)
Details
This is one potential way to reduce load, and already in use in AWS. It's not immediately clear if the AWS architecture can translate seamlessly to scl3.
IT has VMs available if needed.
|
||
Comment 1•10 years ago
|
||
This would reduce cost from S3 -> SCL3 as well.
Old bug, still relevant?
I believe the product delivery migration project addresses the zlb loading, for which this bug was originally filed.
(In reply to Chris AtLee [:catlee] from comment #1)
> This would reduce cost from S3 -> SCL3 as well.
Given current plans, what's the expected "tee shirt size" of the savings? If less than "medium" do we want to bother leaving open?
Flags: needinfo?(catlee)
|
|
||
Comment 3•10 years ago
|
||
We're already using an ftp proxy in SCL3 for S3 resources at least, where most of our artifacts are coming from.
RESO FIXED / WFM?
Status: NEW → UNCONFIRMED
Ever confirmed: false
Flags: needinfo?(catlee)
|
|
||
Updated•10 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(hwine)
Resolution: --- → FIXED
|
Assignee | |
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•