[x] @mrbojangles3 remove all mentions of Management Connections (completely removed)
[x] @mrbojangles3 control chain / chain boot - replaced with OOB management network
[x] @mrbojangles3 add clear statements that all switches mgmt ports and control nodes should be connected to OOB mgmt net and we aren't managing this net, this net should be isolated from everything else and no other devices are recommended on it, no dhcp servers (other then control nodes) should be present on this net, HH not managing management switches, add to system requirements
[x] @mrbojangles3 remove das-boot and honie mentions
[x] @mrbojangles3 remove Server type mentions (type: control) - it's now ONLY "workload" server and doesn't describe a control node
[x] @Frostman we need to document a new field on a switch spec boot (with mac/serial for provisioning)
[x] @mrbojangles3 add info on switch "discovery" to installation docs (MAC of the first management interfaces AND/OR Serial number)
[x] @mrbojangles3 remove any mentions of location and locationSig from switches/servers (if any)
[x] @Frostman update control node requirements (CPU/RAM/good SSD/mgmt & ext interfaces), 10G is preferred
[x] @mrbojangles3 update vlab setup & demo as outputs and some commands are now different
[x] @mrbojangles3 (LOW) add hhfab vlab setup-vpcs / setup-peerings / test-connectivity to the vlab demo page (maybe as a separate exercise in the end)
[x] @Frostman update supported devices
[x] @Frostman make sure API/Profiles refs are latest
[x] @mrbojangles3 update install instructions with a new commands (mention hhfab validate)
Some more things to do:
type: control) - it's now ONLY "workload" server and doesn't describe a control nodehhfab vlab setup-vpcs / setup-peerings / test-connectivityto the vlab demo page (maybe as a separate exercise in the end)