This task will track the racking, setup, and OS installation of lvs10[17-20].
These are required to make use of any services that are behind LVS in eqiad, so the need by is asap.
== Hostname / Racking / Installation Details ==
**Hostnames:** What are the hostnames, and have you updated https://wikitech.wikimedia.org/wiki/Infrastructure_naming_conventions ?
> lvs1017, lvs1018, lvs1019, lvs1020
**Racking Proposal:** Where should these systems be racked? Can they share with any existing systems or should they avoid any other systems sharing their rack or row?
> Must be racked one-per-row in rows A (17), B (18), C (19), D (20). Should be in 10G-capable racks in each row. See below about network cables affecting rack placement.
**Networking/Subnet/VLAN/IP:** What are the network details? 1G or 10G? Only one network port connection, or more? Subnet/vlan and IP requirements per connect?
> Each of the four hosts has 6x 10G ports that will eventually be hooked up. The primary/first 10G interface goes to its own ToR switch in its own row. The other 5 are for cross-row connections.
>
> For the initial replacement/decom of lvs101[3456] - it would be advantageous to place each new server in the same rack as the one it's replacing, as near to the existing lvs server as possible: (new lvs1017 with old lvs1013 in A7, 18 with 14 in B7, 19 with 15 in C7, and 20 with 16 in D7).
>
> We can then, one rack/server at a time, bring up the new lvs and move the existing x-row cables (for ABCD) to the new lvs and decom the old one from service. Then the only truly-new x-row connections will be for future rows E/F (which may not be ready when we initially install these LVSes, which is fine!).
>
> All of those racks seem to have at least 1U slot open. If the cable runs can't move far enough for the new slot, we could also consider a decom-then-install process (remove the old LVS from service, unrack it, rack new LVS in same slot and hook cables back up), but there are resiliency risks so that process would have to be completed in a single day in as short a time window as we can manage.
**Partitioning/Raid:** Is this hardware or software raid and what raid levels should be applied to each disk? What are the partitioning requirements and is there an existing partman recipe?
> Already correct in partman: `lvs*) echo partman/standard.cfg partman/raid1-2dev.cfg ;; \`
**OS Distro:** Buster (default unless otherwise specified)
> Buster
== Per host setup checklist ==
Each host should have its own setup checklist copied and pasted into the list below.
lvs1017:
[] - receive in system on #procurement task T293128 & in coupa
[] - rack system with proposed racking plan (see above) & update netbox (include all system info plus location, state of planned)
[] - bios/drac/serial setup/testing
[] - add mgmt dns (asset tag and hostname) and production dns entries in netbox, run cookbook sre.dns.netbox.
[] - network port setup via netbox, run homer to commit
[] - firmware update (idrac, bios, network, raid controller)
[] - operations/puppet update - this should include updates to install_server dhcp and netboot, and site.pp role(insetup) or cp systems use role(insetup::nofirm).
[] - OS installation & initital puppet run via script
lvs1018:
[] - receive in system on #procurement task T293128 & in coupa
[] - rack system with proposed racking plan (see above) & update netbox (include all system info plus location, state of planned)
[] - bios/drac/serial setup/testing
[] - add mgmt dns (asset tag and hostname) and production dns entries in netbox, run cookbook sre.dns.netbox.
[] - network port setup via netbox, run homer to commit
[] - firmware update (idrac, bios, network, raid controller)
[] - operations/puppet update - this should include updates to install_server dhcp and netboot, and site.pp role(insetup) or cp systems use role(insetup::nofirm).
[] - OS installation & initital puppet run via script
lvs1019:
[] - receive in system on #procurement task T293128 & in coupa
[] - rack system with proposed racking plan (see above) & update netbox (include all system info plus location, state of planned)
[] - bios/drac/serial setup/testing
[] - add mgmt dns (asset tag and hostname) and production dns entries in netbox, run cookbook sre.dns.netbox.
[] - network port setup via netbox, run homer to commit
[] - firmware update (idrac, bios, network, raid controller)
[] - operations/puppet update - this should include updates to install_server dhcp and netboot, and site.pp role(insetup) or cp systems use role(insetup::nofirm).
[] - OS installation & initital puppet run via script
lvs1020:
[] - receive in system on #procurement task T293128 & in coupa
[] - rack system with proposed racking plan (see above) & update netbox (include all system info plus location, state of planned)
[] - bios/drac/serial setup/testing
[] - add mgmt dns (asset tag and hostname) and production dns entries in netbox, run cookbook sre.dns.netbox.
[] - network port setup via netbox, run homer to commit
[] - firmware update (idrac, bios, network, raid controller)
[] - operations/puppet update - this should include updates to install_server dhcp and netboot, and site.pp role(insetup) or cp systems use role(insetup::nofirm).
[] - OS installation & initital puppet run via script
**Once the system(s) above have had all checkbox steps completed, this task can be resolved.**