Form cover
Page 1 of 5

Oxide Rack Pre-Installation Checklist

A. Site Physical Requirements

Equipment Delivery

Equipment Delivery
Crated Rack Dimensions: height (102”), width (59”), and weight (2694 pounds)

Datacenter Environment

Datacenter Environment

Power Type

Power Type
A
B

Rack Placement

Rack Placement
* 41.8" deep with no doors, 23.7” wide without side panels; do not install side panels if the rack has to fit within a standard tile.

Other Requirements

Other Requirements

Initial rack setup

Oxide intends to perform the first-time software update and rack initialization via a jumpbox that will also be used for near-term support after rack deployment. The goal is to exercise the network path, tools and processes involved.

Jumpbox specifications

The jumpbox in question will ideally meet the following requirements:
1. Run on some Unix OS (e.g., Linux, BSD, OmniOS, etc) with OpenSSH client and server
2. Oxide staff must be able to SSH directly from their own machine to the jumpbox and over the VPN, if one is configured:
• For additional security, the access into the rack is restricted by having Oxide’s SSH private keys stored in hardware tokens (Yubikey 5)
• Oxide staff need to be able to forward their token-backed SSH agent through the jump box using some combination of "ssh -J" (ProxyJump) and "ssh -A" (ForwardAgent)
3. Jumpbox will need to be accessible from two networks:
• the VPN that allows Oxide to access SSH on the jumpbox from an outside connection
• direct attachment to the VLAN where the rack techport is connected, to allow the use of IPv6 link local addresses with unicast traffic, router advertisements, and some IPv6 multicast traffic to discover and access the rack itself
4. Accounts:
•Customer may provide Oxide with a single "oxide" account on the jumpbox system
• SSH access will be controlled by the customer and granted to Oxide.
5. Storage:
• Preferably has 100 GB or more disk space
• Expect to be used for copying large software images into jumpbox local storage as a staging area before submitting them to the rack (via scp, rsync, etc)
Expect to be used also for copying large files (e.g. logs, core files, crash dumps) out of the rack with the customer’s consent (Note: There is no phone-home feature or background process that automatically exports data outside of the rack.)

Access control method (if remote support is granted)

The steps for granting one-time rack access will look roughly like the following:
Access control method (if remote support is granted)