Next week dividehex is going to work on getting a recent 10.9 seed image installed on one of the existing talos-mtnlion-r5 machines (to be specified by releng). We have a pretty generic OS X test entry in puppetagain that handles 10.8, 10.7, etc, so our plans are to put in a node definition for the new machine and let it rip. We may have to build new versions of a few tools like python to get a 100% functional machine. Based on https://wiki.mozilla.org/ReleaseEngineering/Slave_Naming we are going to name this host: t-maverick-r5-001.test.releng.scl3.mozilla.com dividehex, please be sure to update inventory (and DS) with the new name and put a note referencing it's past name in the notes section in inventory. Please also open a bug to update nagios (and have them create a new hostgroups for the maverick hosts) when the new host is up.

Loaned talos-mtnlion-r5-087.

Inventory/DNS have been updated

Opps forgot to close this out. The 10.9 seed image has been deployed to t-maverick-r5-001.test.releng.scl3.mozilla.com via DS. I did have a lot of trouble with some of the automation in the work flow but that had to do with the fact that the current puppet and facter packages are incompatible with the version of ruby included in the 10.9. Maverick 10.9 includes Ruby 2.0.0 and previous OSX versions included 1.8.7. PL will more than likely have compatible packages by the time Maverick is released and it should be trivial to add the workflow automation for puppetizing back in at that time also. The new workflow for 10.9 on install.test.releng is titled 'Restore t-maverick-r5' and a new DS group has also been created titled 't-maverick-r5' Root has been enabled and puppet will need to be installed by hand for now (probably via gem). Use the 'Newly kickstarted password' for it's unpuppetized root login.

Amy renamed this to t-mavericks-r5-001. Puppet has messed up the user accounts enough that after an accidental logout, I can't get back in :(