1.2. Host Deployment

The following steps should be followed whenever deploying a new system. This includes systems that are being re-purposed or rebuilt.

1.2.1. Physical Deployments

When deploying a new physical host, the following requirements must be met. This is in addition to the normal host deployments below.

Leased or non-self hosted hardware.

Section 1.2.1 and its subsections are specifically targeted at environments where a machine is physically managed by The Fedora Project. If they are managed by a third party some of these steps are likely delegated to that provider. In that event please exclude any steps that don't apply but do ensure to verify things like the manifest comparison below.

1.2.1.1. Physical Inventory

Each of the below items is to be inventoried.

Inventory Items

Complete	Part	Additional
	Shipping Integrity	Ensure packaging that the server was shipped in is not damaged and that everything seems sane.
	Chassis	Include serial number, part numbers, manufacturer, etc.
	Drive Inventory	Document serial number, part number, size, speed, make and model of each drive in the system.
	Manifest Comparison	Verify the manifest matches what the host actually contains and what was actually ordered. This includes number and speed of processors, RAM, disks, etc.

1.2.1.2. Firmware Updates

Ensure all firmware in the system is up to date prior to use.

Firmware Updates

Complete	Part	Description
	BIOS	Ensure the bios is at the latest available version.
	Drives	Ensure each physical drive is up to date.
	Remote Access	Ensure any remote access modules are updated including BMC, RSA-II, DRAC, iLo, etc.

1.2.1.3. Physical Racking

While racking the server, ensure each requirement is met.

Inventory Items

Step	Requirement	Description
Rail Kit	Must	Install rail kit in rack, install on server.
Mounting	Must	Mount server in the newly installed rail kit.
Vendor Cable Management	Should	Any vendor provided cable management should be installed with the server (usually as an arm on the back of the server). It is acceptable to exclude this if your organizations cable management policies are in conflict with these devices or if they, for whatever reason, are physically unable to fit in the rack.
Network Configuration	Must	Using cable management policies, run cable from your switch or drop points to the ports on the server. Ensure the cable has enough length to remain connected while the server's rail kit is in the fully extended position. Cables should be no more then 3 inches longer then this required length. Follow a common cable coloring standard (not presently covered by CSI)
KVM	May	Those wishing to use a KVM (keyboard, mouse and monitor) may hook them up. Use the provided cable management and ensure the cables are no more then 3 inches longer then required to have the server in it's full out position.
Serial/Remote	Should	In addition to the remote access modules, servers should have an additional remote management method. Serial consoles are popular for this. Ensure the cabling required for this uses provided cable management and is no more then 3 inches longer then required to have the server in it's full out position.
Power	Must	Once the host is installed, ensure power is properly supplied via the provided cable management. Cables should be no more then 3 inches longer then required for the server to be in it's full out position.
POST Check	Must	Once fully installed, power the machine on and very it will post without any errors.

1.2.1.4. Post Racking Checklist

Once the server is fully racked and installed, the following checklist must be completed.

Post Install Checklist

Complete	Task	Description
	PDU Port Config	Ensure each PDU port is inventoried and configured. If the PDU is manageable, ensure the ports are properly labeled.
	Serial Console	If using serial console, ensure it is working (check bios baud rate and Cyclades baud rate).