Hosts
Actual hosts are not yet allocated. Each machine expected to be used has identical specifications, as detailed below.
- Book host, update specifications from observed
HPE x86_64 node:
| Memory | Capacity | 512 GB |
| Technology | DDR4 | |
| Network Interface Type 1 | Count | 4 |
| Speed | 25Gbit | |
| Model | ||
| Network Interface Type 2 | Count | 2 |
| Speed | 10Gbit | |
| Model | ||
| CPU | Socket count | 2 |
| Cores/Socket | 22 | |
| Threads/Core | 2 | |
| Model | ||
| Disk Type 1 | Capacity | ~1TiB |
| Count | 3 | |
| Interface | SATA 3 | |
| Storage Type | SSD | |
| RAID | None | |
| Disk Type 2 | Capacity | ~800GiB |
| Count | 1 | |
| Interface | SATA 3 | |
| RAID | 1 (two 480GiB members) | |
| Storage Type | SSD | |
| Feature Support | RedFish | |
| IPMI | Yes |
Networking
Topology unknown, update once we hear back from Anuket community.
- Update topology, integrate with draft PDF/IDF
Validated descriptor files PDF and IDF might help recognize the network topology we need. They are defined under hw_config/intel as YAML schema and can be used to refer to. The code can be found at https://gerrit.opnfv.org/gerrit/admin/repos/kuberef .
- Draft PDF:
pdf.yaml- Given IDF appears to have two networks with dns/gateway, should oob be routable to outside world, and is that a requirement?
- Yes. If so, do what the given IDF says. Is it going to be difficult?
- Source IDF/PDF uses multiple undeclared private networks for hosts
- Static leases/direct pipes for external traffic
- Can't provide directly assigned static IPs (need to NAT), find out if this is workable or a more exotic solution is necessary
OS Environment
OS is wiped away by kuberef (baremetal deploy), jumphost can be Ubuntu or CentOS
- Find OS variant+version for jumphost
- Access/permissioning for jumphost: keys/accounts for all involved parties (add each as points below this)
PDF/IDF
Draft PDF/IDFs should be updated here (or pointed to from here) describing the aforementioned attributes