Closed
Bug 1491200
Opened 6 years ago
Closed 6 years ago
decommission old mergeduty instance and halt the puppetized existing one
Categories
(Release Engineering :: General, enhancement)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mtabara, Assigned: mtabara)
References
Details
Attachments
(1 file)
61 bytes,
text/x-github-pull-request
|
mtabara
:
checked-in+
|
Details | Review |
1. Seems like we've successfully used puppetized mergeday1 from aws usw2. I think it's safe to halt it for now, until next mergeduty is needed.
2. We can retire our old one Mozilla release staging/merge instance from aws use1. (initial one that Kim added where we used to centralize our operations but was not puppetized). It's now stopped but I think we can retire it completely.
Assignee | ||
Comment 1•6 years ago
|
||
(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #0)
> 1. Seems like we've successfully used puppetized mergeday1 from aws usw2. I
> think it's safe to halt it for now, until next mergeduty is needed.
done - instance terminated.
> 2. We can retire our old one Mozilla release staging/merge instance from aws
> use1. (initial one that Kim added where we used to centralize our operations
> but was not puppetized). It's now stopped but I think we can retire it
> completely.
done - was already stopped.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 2•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → mtabara
Assignee | ||
Comment 3•6 years ago
|
||
Comment on attachment 9009011 [details] [review]
[releasewarrior] cleanup in mergeduty docs
https://github.com/mozilla-releng/releasewarrior-2.0/commit/16a88b5782dbd38fd9ef11e7be7b60b1fb8e8e33
Attachment #9009011 -
Flags: checked-in+
You need to log in
before you can comment on or make changes to this bug.
Description
•