The IOL RI2 pod 1 is currently deployed across 6 hosts. Five hosts (hpe12, hpe29, hpe27, hpe31, and hpe07) make up the k8s deploy, with an additional sixth node as the jumphost (hpe30).
The IOL RI2 pod 2 is deployed with the same topology, with hpe9 as a jumphost, and (hpe16, hpe18, hpe21, hpe37, hpe38) as node1 through node5
HPE x86_64 node:
|Network Interface Type 1||Count||4|
|Network Interface Type 2||Count||2|
|Disk Type 1||Capacity||~1TiB|
|Disk Type 2||Capacity||~800GiB|
|RAID||1 (two 480GiB members)|
The pod has 7 layer 3 networks:
- 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 .
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)
The current IDF and PDF for the pod are idf.yaml and pdf.yaml.
A series of scripts were created to generate configuration files and the PDF/IDF pair for the pod. These files are available in the kuberef repository at <awaiting PR>.