Closed Bug 786712 Opened 12 years ago Closed 11 years ago

coordinate shut down of briar patch

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: hwine, Assigned: hwine)

References

Details

(Whiteboard: [briarpatch] [re-nad-20130515])

We learned a lot, and are already reusing some code in other projects, but there are is no one to carry on with this project. Let's give it the clean shutdown it deserves!

This bug depends on all the open briarpatch bugs I could find. Add/open any others that are needed.
Monitoring was never implemented (https://bugzilla.mozilla.org/show_bug.cgi?id=775285). You shouldn't trigger anything bad if you shut off the boxes. At worst, supervisord might try to keep a proc alive or puppet might rewrite some files you've just deleted.
Depends on: 769673
This was a joint goal with IT and Webdev, I don't feel a joint decision has been made to kill it...  I'd rather not give up on this just yet, especially given the discussion we just had on Tuesday about resourcing releng needs for the future.  This dashboard would help with capacity planning, and from our point of view is still desperately needed.
Depends on: 787582
My apologies - I thought it was only a webdev-releng project. I fully agree that a dashboard is needed. I'll hold off and reach out to you via email
Please involve me, when you do.  Thanks!
No longer depends on: 713020
Per bug 807812, we should think about moving these machines out of private.scl3 if we do decide to keep 'em, or keep the service.
No longer depends on: 787582
all dependent bugs in process of being closed - will check back to verify status in a few weeks.
Whiteboard: [briarpatch] → [briarpatch] [re-nad-20130515]
all done!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.