diff options
author | 2018-11-08 19:06:46 +0100 | |
---|---|---|
committer | 2019-01-09 15:39:05 +0100 | |
commit | 455b46a6be4bca145c047ed6957727c119285796 (patch) | |
tree | 717062888465d74227a45d724fab21e9c8fd5957 /docs/release/scenarios/os-nosdn-fdio-noha/os-nosdn-fdio-noha.rst | |
parent | ad2bdf2eb08c0991757f30d370c90d5c9d814d3e (diff) |
Bring in FDIO (VPP+DPDK) scenario
- cmp, gtw: bump RAM allocation to accomodate hugepages/VPP;
for now we overcommit, gtw01 resources can probably be lowered;
- submodule: add salt-formula-neutron so we can locally patch it;
- repo:
* FD.IO repos for VPP packages;
* networking-vpp PPA for python-networking-vpp Neutron driver;
- use vpp-router for L3, disable neutron-l3-agent;
- baremetal_init: apply repo config before network (otherwise UCA
repo is missing when trying to install DPDK on baremetal nodes);
- arm64: iommu.passthrough=1 is required on ThunderX for VPP on
newer kernels;
Design quirks:
- vpp service runs as 'neutron' user, which does not exist at the
time VPP is installed and initially started, hence the need to
restart it before starting the vpp-agent service;
- gtw01 node has DPDK, yet to configure it via IDF we use the
compute-specific OVS-targeted parameters like
`compute_ovs_dpdk_socket_mem`, which is a bit misleading;
- vpp-agent requires ml2_conf.ini on ALL compute AND network nodes
to parse per-node physnet-to-real interface names;
- vpp process is bound to core '1' (not parameterized via IDF);
Change-Id: I659f7dbebcab7b154e7b1fb829cd7159b4372ec8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Diffstat (limited to 'docs/release/scenarios/os-nosdn-fdio-noha/os-nosdn-fdio-noha.rst')
0 files changed, 0 insertions, 0 deletions