Closed
Bug 895475
Opened 12 years ago
Closed 8 years ago
need non-scl3 linux signing servers again
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: bhearsum, Unassigned)
Details
(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2519] )
When we replaced the Linux signing servers as part of bug 869498 we put all of the new ones in SCL3. The previous generation had 2 in SCL1, and 1 in SCL3, giving us some form of redundancy. As things stand now, having signing servers elsewhere wouldn't help much, because nearly all of our build machinery is in SCL3 and AWS (which depends on SCL3 for routing), but we should still strive to remove SPOFs like this.
We have great puppet manifests for the signing servers, so if we chose a place (scl1? aws?) it should be pretty easy to bring them up.
|
Assignee | |
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
|
||
Updated•11 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2519]
|
|
||
Comment 1•8 years ago
|
||
We'll tackle this once we start populating the new data centers as part of the SCL3 evacuation.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
|
|
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
•