This task will track the racking, setup, and OS installation of cloudswift100[12]
Hostname / Racking / Installation Details
Hostnames: cloudswift1001, cloudswift1002
Racking Proposal: Use WMCS dedicated 10G racks. These can be placed in any WMCS rack and co-exist with any WMCS service. However, please place each in a separate rows from one another.
Networking/Subnet/VLAN/IP: two 10G connections. Current networking not certain, possibly cloud-hosts1-eqiad for primary and another vlan (non wmcs?) for secondary connection. This will need to be determined before the systems arrive on-site. - see below networking section
Partitioning/Raid: standard, raid1-2dev
OS Distro: Bullseye
Technical Contact: @aborrero
Networking Details
Discussion on purchase task T286586 denotes this is a new service, and the networking requirements are not entirely known at time of system order placement. The networking will need to be determined before the hosts arrive (approximately 20 days), so both cloud-services-team (Hardware) and netops have been added as project tags, and the relevant users subscribed at time of task creation. The discussion on the purchase task assumes this will need to use both of its 10G ports, with one likely in the cloud hosts vlan (primary port) and one likely in another vlan (unknown at this time.) This service will be consuming ceph/rbd and presenting it to the public internet.
Per host setup checklist
Each host should have its own setup checklist copied and pasted into the list below.
cloudswift1001:
- - receive in system on procurement task T286586 & 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 wmf-auto-reimage or wmf-auto-reimage-host
- - host state in netbox set to staged
cloudswift1002:
- - receive in system on procurement task T286586 & 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 wmf-auto-reimage or wmf-auto-reimage-host
- - host state in netbox set to staged
Once the system(s) above have had all checkbox steps completed, this task can be resolved.