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)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mtabara, Assigned: mtabara)

References

Details

Attachments

(1 file)

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.
(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: nobody → mtabara
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: