[#334] Add CPU Manager for Kubernetes (CMK) to CNF Testbed

michaelspedersen commented 4 years ago

This PR does the following:

Adds isolcpus argument to Makefile, which will update GRUB on worker nodes with CPU isolation (similar to what is being done when deploying vSwitch)
Updates the grub_vswitch Ansible role, as the CPUs in n2.xlarge.x86 (and maybe others) don't always match the described/expected CPU (16 cores instead of 14)
Adds go-gtp-ubuntu network_functions example. Similar to go-gtp, but based on Ubuntu 18.04 instead of Alpine (due to cross-compatibility issues with CMK)
Adds cpu-manager workload_infra example. Deploys CPU Manager for Kubernetes on each worker, with 11 exclusive and 2 shared cores per socket.
Adds gogtp-k8s/k8s_bridged_cmk use_case example. Similar to k8s_bridged_networks example, but with each workload/application having CPU affinity assigned through CMK

Issues

cncf/cnf-testbed#334

How Has This Been Tested?

[x] Tested locally
[ ] Have not tested

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] No updates required.

nickolaev commented 4 years ago

Hmm, why mix GoGTP and isolcpus. They have no relation at all.

michaelspedersen commented 4 years ago

Hmm, why mix GoGTP and isolcpus. They have no relation at all.

I would say they have as much relation as any use-case at this point. While not focusing on performance in particular, I still consider CPU isolation/affinity relevant for anything in telco deployments that interacts with a data plane.

I will agree that there are far better use-cases for it, e.g. dpdk applications running poll-mode, but I'd rather avoid creating a new use-case for every "piece" of infrastructure tooling that we add to the testbed.

cncf / cnf-testbed