Closed Bug 694703 Opened 14 years ago Closed 14 years ago

Set up new mac minis on QA vlan with assigned names in DNS

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: abillings, Assigned: dustin)

Details

QA has 12 new(ish) mac minis: 1. 8 brand new running OS X 10.7 2. 4 repurposed ones running OS X 10.6 These are being set up in 2/IDF, per Zandr. These need to be put onto the QA vlan when they are set up. I want to use the following naming scheme. For the 8 10.7 machines: release<x>-osx-107.qa.mtv1.mozilla.com the <x> above will be replaced with the numbers 1 through 8 with a unique number on each machine. For the 4 10.6 machines: release<x>-osx-106.qa.mtv1.mozilla.com with the numbers 1 through 4. These names should be added to DNS so they can be reliably reached by name only. Does this make sense?
colo-trip: --- → mtv1
Inventory details here please - switchports, rack, rack position, serials, asset tags. I'll update inventory.
I'm revoking the "please" in my previous comment. DO NOT MOVE THESE UNITS without providing inventory information. If they're already moved, find the inventory information.
I've got two additional 10.5 OS X mac minis on my desk on floor 3 that are to go onto this network. See Bug 696475 and Bug 696528.
Thanks. I'm mostly concerned about the inventory for the r4 minis because they're coming *out* of a pool where I'm trying to track down the stragglers, but I'll make sure those two minis get their inventory updated as well.
According to Al, all 12 of these (repurposed r4's from releng, and 8 new) are on matt's desk.
So, six of the machines from releng were racked and imaged, which is two too many. The downside of coordinating work via IRC! I've allocated four to QA, as requested. These are named as in comment 0, and have IPs 10.250.73.{20..22}. The user is 'qa', SSH and VNC are enabled, and I or digi can give you the password via IRC PM. You should be good to go on those. https://inventory.mozilla.org/systems/show/4553/ https://inventory.mozilla.org/systems/show/4554/ https://inventory.mozilla.org/systems/show/4555/ https://inventory.mozilla.org/systems/show/4556/ This bug remains open for the 8 new lion minis, which were *not* on Matt's desk, so someone familiar with local goings-on will need to track those down.
I can ssh into the 10.6 boxes but I cannot VNC, as I'm getting a different password prompt (for a VNC password, it seems) and the password I was given for the QA account does not work there. Since Apple Remote Desktop is not installed, I'm limited to SSH right now. I'm not sure how to (re)set the VNC password from command line on OS X.
http://hg.mozilla.org/build/tools/file/default/buildfarm/maintenance/update_remote_creds.pl#l341 has sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -configure -activate -access -on -clientopts -setvnclegacy -vnclegacy yes -setvncpw -vncpw $vnc_password -restart -agent I'm not sure why the VNC password would be different by default, but there you are.
I tried this script, putting in a value for $vnc_password, and I still cannot get in with VNC or Apple Remote Desktop (which this appears to turn on given that it is the ARD Agent). When using Remote Desktop, my 'qa' account credentials fail when prompted. When using VNC, with the 'qa' account, I get prompted for a password and that fails no matter whether I enter my new VNC password or the qa account password. If someone knows how to get this working, I'd appreciate it. We're running UI content on these machines so I need UI access.
Have you tried using ARD to (re)install the ARD agent on the clients? I don't know much about ARD and VNC, honestly.
I've run the script from the above comment with my own password. sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -configure -activate -access -on -clientopts -setvnclegacy -vnclegacy yes -setvncpw -vncpw $vnc_password -restart -agent Who can we cc who would know more here than us?
I've fixed remote. There is a bigger problem though. release3-osx-106.qa.mtv1.mozilla.com and release-4 are both pointing to the same machine, which is on .22 for its IP. If I go to release3-osx-106 or release4-osx-106, I get the same machine. So I only have access to three mac minis, not four. Where is the fourth?
In both comment 6 and DNS, I typo'd '22' for '23' referring to release4-osx-106. That's been fixed now, and the DNS should propagate in a few minutes
This is working now. release1 through 4-osx-106 and release1 - 3-osx-105 are all up and running.
(Vinh Hua from bug 674700 comment #27) > Hi Al, > To my knowledge, the 8 Mac Minis are sitting in the server room waiting to > be set up by Zandr. At a guess, they are in 3.MDF, then. Tracking.
The word from Matt, who checked as a favor to me, is that they are not in 3.MDF. Vinh's our best bet for finding these, now.
They are sitting in the 2nd floor IDF room. I've just shown Matt where they are.
Confirmed. There are 8 boxed minis there, and sufficient sonnet chassis to place them in. They are not yet asset-tagged. We'll probably knock these out next week. Thanks, Matt!
Assignee: zandr → dustin
I am assigning this to me for the time being to get them in Chassis, racked, powered and connected to the switch. The vlan is already setup for abillings in 2/IDF so I will rack them in there as well above the Mac Pro's granted there is room(Which I believe there is).
Assignee: dustin → mlarrain
Cool. If you feed me: asset tag serial MAC switchport rack position in this bug, I'll get them online. These will need to be crash-carted through the welcome-to-mac screens, and then have SSH and VNC enabled. They should be running lion, not snow leopard.
Put mini's into there chassis's and racked them in 2/IDF Will update with asset tag's, serials, MAC, switchport and rack position as soon as we can squeeze a crash cart in there and get the cabling done.
I'll finish this up next week. Thanks, Matt!
Assignee: mlarrain → dustin
So I un-racked these to crash-cart, and at least one of them is already set up. Waiting to hear from Al as to how I should proceed - I need to login to get MAC and serial info. They're (where else?) on Matt's desk for the moment.
These are already installed, and at least have 'qaN' set up, with N for each machine. Per abillings, I'll wipe and re-image them with 10.7.
07638 is bad. I've filed bug 701250 to get it repaired. For the moment, its partner in the sonnet chassis (07640) is offline, but it is fully installed and can be racked when 07638 is back.
Comment 25 was incorrect - it just needed its pram zapped. All 8 are now racked in 2.IDF and powered on. I haven't set up DHCP yet - I'll get to that shortly.
Hooray! I've successfully SSH'd into all 8 of the new mac minis. I believe that closes this bug. Please check as thoroughly as possible, and re-open with any problems that will require further hands-on work. I have a very limited amount of time in mtv1 on Friday, so I can fix any problems that I know about at that point.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.