Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Hosts

Actual hosts are not yet allocated. Each machine expected to be used has identical specifications, as detailed below.

...

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:




Memory

Capacity

512 GB

TechnologyDDR4



Network Interface Type 1Count4

Speed25Gbit

Model
Network Interface Type 2Count2

Speed10Gbit

Model



CPUSocket count2

Cores/Socket22

Threads/Core2

Model



Disk Type 1Capacity~1TiB

Count3

InterfaceSATA 3

Storage TypeSSD

RAIDNone
Disk Type 2Capacity~800GiB

Count1

InterfaceSATA 3

RAID1 (two 480GiB members)

Storage TypeSSD



Feature SupportRedFish

IPMIYes

Networking

...

RI2 pod 1 has 7 layer 3 networks:

NameDHCP ProvidedSubnetGatewayNetmaskUnderlay VLAN
publicno10.200.120.010.200.120.124120
oobno10.200.122.0N/A24122
mgmtno10.200.123.010.200.123.124123
private_1no127.0.101.0N/A24201
private_2no127.0.102.0N/A24202
private_3no127.0.103.0N/A24203
private_4no127.0.104.0N/A24200


RI2 pod 2 also has 7 layer 3 networks, with different underlay vlans:

NameDHCP ProvidedSubnetGatewayNetmaskUnderlay VLAN
publicno10.200.138.010.200.120.124138
oobno10.200.111.0N/A24111
mgmtno10.200.128.010.200.123.124128
private_1no127.0.101.0N/A24210
private_2no127.0.102.0N/A24211
private_3no127.0.103.0N/A24212
private_4no127.0.104.0N/A24209


The jumphost has the following connections by interface name:

InterfaceNetworkHandles Default RouteIP
ens1f0mgmtyes10.200.123.11
ens1f1oobno10.200.122.16


Each host is connected to networks as follows:

InterfaceNetworkHandles Default RouteIP
ens1f0oobno<subnet>.<node # + 10>
ens1f1publicyes<subnet>.<node # + 10>
eno49private_2no<subnet>.<node # + 10>
eno50private_3no<subnet>.<node # + 10>
ens4f0private_4no<subnet>.<node # + 10>


  •  Update topology, integrate with draft PDF/IDF
  •  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
    •  

      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 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

...

The current IDF and PDF for the pod are idf.yaml and pdf.yaml.

Generation Scripts

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>.


The versions used to create the current deployment of the pod are attached to this page as install.py and gen_net_configs.py