Closed Bug 456485 Opened 16 years ago Closed 15 years ago

Move talos masters instances onto staging-master & production-master VMs

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: nthomas, Unassigned)

Details

We've been moving masters over to staging/production-master, which is currently running Buildbot 0.7.7. That's complete for unittest so we should think about doing this for Talos too before it gets left too far behind.
In this bug, we'll need to: 1) update buildbot version on master to match what is already used for build+unittest masters 2) confirm its ok to not update the slaves, despite updating the masters 3) once talos instance moved to run on staging-master & production-master, we can mothball qm-rhel02 Separate to this bug is additional work being discussed to consolidate different instances into one staging-master instance and one production-master instance.
Component: Release Engineering: Talos → Release Engineering: Future
Summary: Move talos masters from qm-rhel02 & Buildbot 0.7.5 → Move talos masters instances onto staging-master & production-master VMs
Can't see us doing this given that we purposely reduced load on production-master already.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.