If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

adding bulk k/v store info to all hosts in scl1

RESOLVED FIXED

Status

Infrastructure & Operations Graveyard
WebOps: Inventory
RESOLVED FIXED
4 years ago
a year ago

People

(Reporter: arr, Assigned: uberj)

Tracking

Details

Attachments

(2 attachments)

(Reporter)

Description

4 years ago
In the meeting we had today about decomming scl1 we talked about adding an inventory k/v to track what the intended plan was for all of the hardware. I'd like to bulk add a key and some default values so that we can start reporting on this.

1. ignore any host entry that's already marked as decommissioned and do not add this key.
2. ALL other scl1 inventory entries should start out with the following k/v (listing tbd as to be determined, which should make it easy to sort and search on later to catch all the stragglers):
scl1-decomm tbd

Then we start adding some specific values for the key scl1-decomm following host regexes:

host regex        value

talos-r3%         decommission
linux64-ix-slave% decommission
linux-ix-slave%   decommission
releng-puppet%    decommission
buildbot-master%  decommission


bld-centos6-hp%   replace
bld-linux64-ix    replace
w64-ix%           replace

talos-r4%         migrate
EDID%             migrate
panda%            migrate
foopy%            migrate
mobile-imaging%   migrate


dmoore: I presume you also want to migrate the PDUs?
(In reply to Amy Rich [:arich] [:arr] from comment #0)

> dmoore: I presume you also want to migrate the PDUs?

The majority, if not all, of the PDUs will be useless to us in SCL3.
(Assignee)

Comment 2

4 years ago
What should the key be? 'migration.scl1' ?
(Reporter)

Comment 3

4 years ago
I just picked "scl1-decomm."  We could also call it decomm.scl1 if we want to have a similar flag for different datacenters.  dmoore, do you have a preference (you're going to be closing the datacenters when that happens, so if you want something more generic...).
(Reporter)

Updated

4 years ago
Flags: needinfo?(dmoore)
(Reporter)

Comment 4

4 years ago
Talked briefly with dmoore about this in the engops meeting, and we'll go with decomm.scl1
Flags: needinfo?(dmoore)
(Assignee)

Comment 5

4 years ago
Created attachment 793524 [details]
Outlined keys and which systems are getting said keys

I've outlined which systems I'm going to assign certain keys to (see attachment). :arr can you look these over and let me know if the lists look good?
Flags: needinfo?(arich)
(Reporter)

Comment 6

4 years ago
It looks like you did not omit machines that are already decommissioned, so that's going to give us a bunch of false positives.  Please don't tag anything that's already been decommissioned.

What I didn't see was all of the rest of the gear in scl1 which should be listed as tbd. Routers, switches, kvm servers, vms, rabbit servers, etc.  Did you just omit those and are adding them before you do the attached modifications?  We'll definitely need all of those tagged as well.
Flags: needinfo?(arich)
(Assignee)

Comment 7

4 years ago
Created attachment 793594 [details]
Amended list

Sorry, that first list was very wrong and didn't really capture the systems you had specified.

Let me know if this list looks better and if we need to tweak it more.
Flags: needinfo?(arich)
(Reporter)

Comment 8

4 years ago
Ah, great, that looks much better!  There's a bunch of tbd stuff in there that I'll need to go back and update by hand as we figure out what we're doing with it, but that's the lion's share and will save me (and dcops, netops, and melissa) a huge amount of time.  Thanks!
Flags: needinfo?(arich)
(Assignee)

Comment 9

4 years ago
Okay, I will add these keys and R/F this bug when they are in place.
(Assignee)

Comment 10

4 years ago
For posterity's sake, here is the script used to add the keys:

https://github.com/mozilla/inventory/blob/master/scripts/decomm_scl1.py
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.