Closed
Bug 1244790
Opened 8 years ago
Closed 8 years ago
decomission vcssync1 & vcssync2
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Unassigned)
References
Details
Attachments
(1 file)
3.63 KB,
patch
|
arich
:
review+
hwine
:
checked-in+
|
Details | Diff | Splinter Review |
Services are now running from developer services AWS account - these are no longer needed. Steps needed: - remove from Nagios monitoring - terminate instances - delete storage
Reporter | ||
Updated•8 years ago
|
Assignee: nobody → hwine
Reporter | ||
Comment 1•8 years ago
|
||
Pull monitoring from vcssync{1,2} Some checks appear to have _only_ been for these boxes, so want verification that pulling the whole check was correct. (disk-/ & disk-/opt)
Attachment #8714391 -
Flags: review?(arich)
Comment 2•8 years ago
|
||
Comment on attachment 8714391 [details] [diff] [review] decom-vcssync.patch Review of attachment 8714391 [details] [diff] [review]: ----------------------------------------------------------------- I think you've captured everything correctly. Let me know when you check stuff in, and I can force an svn up and puppet run on the nagios server.
Attachment #8714391 -
Flags: review?(arich) → review+
Reporter | ||
Comment 3•8 years ago
|
||
Comment on attachment 8714391 [details] [diff] [review] decom-vcssync.patch $ svn commit Sending modules/nagios/manifests/releng/hostgroups.pp Sending modules/nagios/manifests/releng/scl3.pp Sending modules/nagios/manifests/releng/servicegroups.pp Sending modules/nagios/manifests/releng/services.pp Transmitting file data .... Committed revision 114602.
Attachment #8714391 -
Flags: checked-in+
Reporter | ||
Comment 4•8 years ago
|
||
this appears to have deployed correctly, no longer see these hosts listed in nagios.
Status: NEW → ASSIGNED
Reporter | ||
Comment 5•8 years ago
|
||
Nagios alerts are gone, someone with AWS chops needs to do rest.
Assignee: hwine → nobody
Status: ASSIGNED → NEW
Reporter | ||
Comment 6•8 years ago
|
||
(aws_manager)[buildduty@aws-manager2.srv.releng.scl3.mozilla.com cloud-tools]$ aws_manage_instances status vcssync{1..2} 2016-02-18 16:52:34,896 - INFO - Found vcssync1 (i-c38fc2f7)... Name: vcssync1 ID: i-c38fc2f7 IP: 10.132.48.15 Enabled: True State: stopped Tags: FQDN -> vcssync1.srv.releng.usw2.mozilla.com, moz-state -> ready, moz-type -> vcssync, Name -> vcssync1, created -> 2013-10-10 21:25:42 PST ======================================================================== 2016-02-18 16:52:34,914 - INFO - Found vcssync2 (i-b0d76287)... Name: vcssync2 ID: i-b0d76287 IP: 10.132.49.15 Enabled: True State: stopped Tags: Name -> vcssync2, moz-type -> vcssync, created -> 2013-10-10 21:39:15 PST, FQDN -> vcssync2.srv.releng.usw2.mozilla.com, moz-state -> ready ========================================================================
Comment 7•8 years ago
|
||
I just disabled termination protection and marked both to be terminated....
Reporter | ||
Comment 8•8 years ago
|
||
Can you check if they are fully gone now, please? If so, r/f the bug and gather endorphins!
Flags: needinfo?(bugspam.Callek)
Comment 9•8 years ago
|
||
I have the gut feeling there may be some ebs lying dormant from these hosts, but I couldn't find a good way to correlate. Anyway, the host instances themselves are gone.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(bugspam.Callek)
Resolution: --- → FIXED
Reporter | ||
Updated•8 years ago
|
Blocks: legacy-vcssync-decom
Comment 10•8 years ago
|
||
Deleted A and PTR records from inventory.
You need to log in
before you can comment on or make changes to this bug.
Description
•