- - mgmt dns entries created/updated (both asset tag & hostname)
- - system bios and mgmt setup and tested
- - network switch setup (port description & vlan)
- - production dns entries created/updated (just hostname, no asset tag entry)
- - install-server module updated (dhcp and netboot/partitioning)
- - install OS (note jessie or trusty)
- - accept/sign puppet/salt keys
- - service implementation
Very happy to see this chugging along!
This will be a Trusty box. Note also that the network setup for labnet1001 is weird, and labnet1002 needs the same setup. I believe that eth1,2,3 are bonded and eth0 has a separate connection; hopefully you can just look at 1001 and copy the setup.
The 10G upgrade was somehow neglected in the moving and allocation of the server (my bad.)
I've created https://rt.wikimedia.org/Ticket/Display.html?id=9407 to track the quote/order of said NIC.
I disabled the internal nic and got the console unstuck. I assume some cables need to be switched around now, so that that the 10g interface can act as the new eth0 and eth1 during startup.
Now, how do we switch to actually using this box? One option is
Another option is to try to do some clever in-place swapping where labnet1002 steps into the role of labnet1001 without the instances noticing... I've no idea how to make that happen though.
I've no idea how to make that happen though.
Well, that's not exactly true. It is /probably/ as simple as changing
templates/wmnet:eth4-1102.labnet1001 1H IN A 10.68.16.1
templates/wmnet:eth4-1102.labnet1002 1H IN A 10.68.16.1
And then restarting nova-network on labnet1002. Scary, though!