Closed
Bug 1066189
Opened 10 years ago
Closed 10 years ago
mark tegra infrastructure as decommissioned in inventory and remove dns/dhcp/site info
Categories
(Infrastructure & Operations :: RelOps: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: arich, Assigned: arich)
References
Details
Attachments
(1 file)
|
10.01 KB,
text/plain
|
Details |
We need to shut down all of the tegra infrastructure and mark it as decommissioned. We then want to remove the dns/dhcp/site stuff (like we did for the stuff in scl1) and get rid of the network flows.
|
Assignee | |
Comment 1•10 years ago
|
||
Attached is the list of hosts that were production and are now marked as decommissioned.
|
|
Assignee | |
Updated•10 years ago
|
Assignee: relops → arich
|
|
Assignee | |
Comment 2•10 years ago
|
||
Uberj: can we move the decommed stuff out of the tegra.releng.scl3.mozilla.com name under the decommissioned name like we did with scl1 gear?
Flags: needinfo?(juber)
|
|
Assignee | |
Comment 3•10 years ago
|
||
ubjer: do we have a projected date to complete this?
|
||
Comment 4•10 years ago
|
||
Changes staged in dev. Can you glance at https://inventory-dev.allizom.org/en-US/core/search/#q=%28tegra%20OR%20foopy%29%20AND%20removed and see if everything looks okay? If it does I can run my script in prod
Flags: needinfo?(juber)
|
|
Assignee | |
Comment 5•10 years ago
|
||
That still seems to leave quite a few things in the domain: https://inventory-dev.allizom.org/en-US/core/search/#q=tegra.releng.scl3.mozilla.com
|
|
Assignee | |
Updated•10 years ago
|
Flags: needinfo?(juber)
|
|
||
Comment 6•10 years ago
|
||
I was going off the list in #c1 . I've reran my script to handle everything under tegra.releng.scl3.mozilla.com. Does it look okay now? (see https://inventory-dev.allizom.org/en-US/core/search/#q=tegra.releng.scl3.mozilla.com)
Flags: needinfo?(juber)
|
|
Assignee | |
Comment 7•10 years ago
|
||
That looks better, thanks! Can we then also delete the entire vlan/forward/reverse zones for tegra.releng.scl3.mozilla.com?
|
|
||
Comment 8•10 years ago
|
||
The script has been ran against prod. tegra.releng.scl3.mozilla.com is, from Inventory's point of view, part of the mozilla.com zone so it will have been cleaned up already. Do you happen to remember what the reverse zones were?
|
|
Assignee | |
Comment 9•10 years ago
|
||
https://inventory.mozilla.org/en-US/core/network/492/
|
|
||
Comment 10•10 years ago
|
||
looks pretty empty. are we done?
|
|
Assignee | |
Comment 11•10 years ago
|
||
What I meant was we should delete that range entirely since it's no longer in use.
|
|
Assignee | |
Comment 12•10 years ago
|
||
And ot be clear, the same with tegra.releng.scl3.mozilla.com. Not JUST removing the hosts in it, but deleting the information from inventory about those vlans/dhcp ranges, etc. Wipe all references to them out completely.
|
|
Assignee | |
Comment 13•10 years ago
|
||
Dave, can you please delete the stuff on the switch/firewall side? Everything related to the tegra vlan should go away now.
Flags: needinfo?(dcurado)
|
||
Comment 14•10 years ago
|
||
The configuration for the tegra vlan has already been removed from the core switch (core1.releng.scl3)
and the firewall (fw1.releng.scl3).
So for all intents and purposes, tegra == toast.
But, 2 aggregation switches still have the vlan configured on some ports, and some of those ports
are up. Are those hosts that are sitting there doing nothing?
(I imagine I'm going to have to get the mac addresses from the switches, then correlate those
to the arp cache on the firewall or border routers, then do a host look up on every one... in
order to answer this question... which I am not excited about)
------------------------------------------------------------
switch1.r202-10.ops.releng.scl3.mozilla.net:
------------------------------------------------------------
tegra 284 ae0.0*, ge-0/0/10.0, ge-0/0/11.0, ge-0/0/12.0*, ge-0/0/13.0*,
ge-0/0/14.0*, ge-0/0/15.0*, ge-0/0/16.0*, ge-0/0/17.0*,
ge-0/0/18.0*, ge-0/0/19.0*, ge-0/0/20.0*, ge-0/0/21.0*, ge-0/0/22.0*
ge-0/0/10 up down
ge-0/0/10.0 up down eth-switch
ge-0/0/11 up down
ge-0/0/11.0 up down eth-switch
ge-0/0/12 up up
ge-0/0/12.0 up up eth-switch
ge-0/0/13 up up
ge-0/0/13.0 up up eth-switch
ge-0/0/14 up up
ge-0/0/14.0 up up eth-switch
ge-0/0/15 up up
ge-0/0/15.0 up up eth-switch
ge-0/0/16 up up
ge-0/0/16.0 up up eth-switch
ge-0/0/17 up up
ge-0/0/17.0 up up eth-switch
ge-0/0/18 up up
ge-0/0/18.0 up up eth-switch
ge-0/0/19 up up
ge-0/0/19.0 up up eth-switch
ge-0/0/20 up up
ge-0/0/20.0 up up eth-switch
ge-0/0/21 up up
ge-0/0/21.0 up up eth-switch
ge-0/0/22 up up
ge-0/0/22.0 up up eth-switch
------------------------------------------------------------
switch1.r202-9.ops.releng.scl3.mozilla.net
------------------------------------------------------------
tegra 284 ae0.0*, ge-0/0/2.0*, ge-0/0/3.0*, ge-0/0/4.0*,
ge-0/0/5.0*, ge-0/0/6.0, ge-0/0/7.0, ge-0/0/32.0*,
ge-0/0/33.0*, ge-0/0/34.0*, ge-0/0/35.0*, ge-0/0/36.0*,
ge-0/0/37.0*, ge-1/0/1.0, ge-1/0/2.0*, ge-1/0/3.0*,
ge-1/0/4.0*, ge-1/0/5.0*, ge-1/0/6.0, ge-1/0/7.0
ge-0/0/2 up up
ge-0/0/2.0 up up eth-switch
ge-0/0/3 up up
ge-0/0/3.0 up up eth-switch
ge-0/0/4 up up
ge-0/0/4.0 up up eth-switch
ge-0/0/5 up up
ge-0/0/5.0 up up eth-switch
ge-0/0/6 up down
ge-0/0/6.0 up down eth-switch
ge-0/0/7 up down
ge-0/0/7.0 up down eth-switch
ge-0/0/32 up up
ge-0/0/32.0 up up eth-switch
ge-0/0/33 up up
ge-0/0/33.0 up up eth-switch
ge-0/0/34 up up
ge-0/0/34.0 up up eth-switch
ge-0/0/35 up up
ge-0/0/35.0 up up eth-switch
ge-0/0/36 up up
ge-0/0/36.0 up up eth-switch
ge-1/0/1 up down
ge-1/0/1.0 up down eth-switch
ge-1/0/2 up up
ge-1/0/2.0 up up eth-switch
ge-1/0/3 up up
ge-1/0/3.0 up up eth-switch
ge-1/0/4 up up
ge-1/0/4.0 up up eth-switch
ge-1/0/5 up up
ge-1/0/5.0 up up eth-switch
ge-1/0/6 up down
ge-1/0/6.0 up down eth-switch
ge-1/0/7 up down
ge-1/0/7.0 up down eth-switch|
|
Assignee | |
Comment 15•10 years ago
|
||
My guess is that the switch ports that are still showing as active are PDUs. DCOps, can you please make sure that those are moved/shut down and that any information in inventory for them is updated so that they do not appear in the tegra VLAN?
Flags: needinfo?(vle)
Flags: needinfo?(vhua)
Flags: needinfo?(sespinoza)
|
|
||
Comment 16•10 years ago
|
||
Wow, that's a lot of PDUs. I needed, I can go through the tracing exercise I described. (I just wish we didn't have to resort to that kind of labor intensive effort.)
|
||
Comment 17•10 years ago
|
||
the PDUs have been shut down a while back. These are actually the iX Foopies. Did we ever receive a bug to unrack or decommission these hosts? I might have missed it. If not, can you send us a list of the retired iX foopies or we can figure it out by the switch ports.
Flags: needinfo?(vle)
|
|
Assignee | |
Comment 18•10 years ago
|
||
The bug was to decommission ALL tegra infrastructure (foopies, boards, the whole works), yes.
|
||
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/353]
|
|
||
Comment 19•10 years ago
|
||
we've removed/unracked these tegra foopies.
Flags: needinfo?(vhua)
Flags: needinfo?(sespinoza)
|
|
Assignee | |
Comment 20•10 years ago
|
||
dcurado: have all the ports shut down now that van has removed the decommissioned servers?
|
|
||
Comment 21•10 years ago
|
||
no. It's on my list. (aside: now that we're down to 2 engineers, forward progress has stalled, and in fact I'm not even treading water. My bug queue has doubled in size, and is growing. So, your patience is appreciated.)
|
|
||
Comment 22•10 years ago
|
||
The network configuration has been deleted from the switches mentioned in comment 14
|
|
Assignee | |
Comment 23•10 years ago
|
||
Sorry, dave, my question wasn't have you removed the configs, just that the ports you saw as active weren't anymore (to make sure that there weren't more stragglers that dcops needed to remove). It sounds like the answer there was yes and you've gone ahead and removed the switch configs, thanks! I went ahead and deleted the network ranges in inventory as well.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(dcurado)
Resolution: --- → FIXED
|
||
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/353]
You need to log in
before you can comment on or make changes to this bug.
Description
•