Good idea, before we start entering data we need to add validators to prevent entry mistakes (regex for the format, maybe coherence in the numbering) and prevent ID-less racks in the relevant sites.

i don't mind filling these in once we have a format.
@RobH do you know C1's labeling layout? I honestly don't recall seeing it. if you have examples for the two cr racks, i can figure out the rest.

The most recent request to access our cage from CyrusOne listed our 'door' as Cage Door 7006.066. IIRC our racks are then labeled based from that.

The portal shows the following 'cages'

1301.DH005.5081.027
1301.DH007.7006.066

1301.ST0726

I'll email in and ask for the rack IDs in our two DH spaces.

3621872 opened, listed myself and Jenn on notify list.

Support,

We recently had to open a case and refer to a rack in our datahall 7, but our rack IDs are not the same rack IDs as CyrusOne uses.

Would it be possible for someone to let me know our entire rack ID list for the following two datahalls:

1301.DH005.5081.027

We have 2 rows (Wikimedia ID E and F) of 5 racks each in this datahall, starting with E1 closest to the door and F5 furthest from the door.

1301.DH007.7006.066

We have 4 rows of 8 cabinets each (Wikimedia ID of rows A, B, C, D), rack A1 closest to the door and D8 furthest. We'd like to know what the Cyrusone IDs are for these cabinets.

Your assistance in getting the Cyrusone assigned rack IDs for our racks would be appreciated. Thank you!

So they're saying they don't have rack IDs but in the recent power incident, they did list the racks by their tile number. So I think that's gonna be our best bet for doing this. Do we want to do it long form like :

1301.DH005.5081.027
1301.DH007.7006.066

Or shorten it to just

5081.027
7006.066

The short form should be enough. The 1301 is the building number I believe, the DH00# is the hall number, but the hall number is also notated by the first number in the third set. The long form technically has more info, but the short could be understood with a simple explanation. I do not mind either way and would like feedback.

Thanks Jenn, I'm good with either. As long as we're able to reference back which one goes to which.

If we're not listing the full info in the rack, perhaps we can in the row? The facility landing page doesn't really have a good spot for it (my prefernce is just list the full thing per rack so copy paste for tickets to facility is easier):

codfw facility landing page: https://netbox.wikimedia.org/dcim/sites/9/
codfw row a landing page (I appended in the 1301.DH007 to it for an example here): https://netbox.wikimedia.org/dcim/locations/11/

If we like this, I can also update the eqiad rows to reflect their two cages in the same manner.

Please note I just appended the cage IDs into the 'notes' field for both codfw and eqiad (so thats new info and perhaps that is good enough for recording the cages so its not needed on row.)

@RobH Please use netbox-next for tests, to avoid the risk of having invalid/stale date in the prod instance until we come to a full agreement and proper data handling.

Note that the plan for Netbox's location field is to match availability zones, see T333948: Improve Netbox "locations" use

@Jhancock.wm the main question is "what is this data going to be used for?"
For example if it's to reference a rack to the DC "Hello CO, we don't have power in rack X", if X is the short version "5081.027" then it might not be enough.

I didn't think about it that way. So we should use long form. The numbers we received in the incident report indicate that the racks are identified by which tile the front of the rack falls onto.

i'm entering the facility id for everything into netbox-next (which i keep forgetting exists ty) for testing. hopefully they can be merged in instead of someone having to re-enter them manually
A1 = 1301.DH007.7010.066
A2 = 1301.DH007.7010.067
A3 = 1301.DH007.7010.068
A4 = 1301.DH007.7010.069
A5 = 1301.DH007.7010.070
A6 = 1301.DH007.7010.071
A7 = 1301.DH007.7010.072
A8 = 1301.DH007.7010.073

B1 = 1301.DH007.7013.066
C1 = 1301.DH007.7018.066
D1 = 1301.DH007.7021.066
E-1 = 1301.DH005.5077.026
F1 = 1301.DH005.5074.026
F2 = 1301.DH005.5074.025
F3 = 1301.DH005.5074.024
F4 = 1301.DH005.5074.023
F5 = 1301.DH005.5074.022

i put these in here in case we don't get this to a point we can enter it into production netbox before i go on vacation.