X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;f=docs%2Freport%2Fvpp_performance_tests%2Fdocumentation%2Fcontainers.rst;h=5ec7d9c112d0ff28bb4e608b7b4007b6c2e93904;hb=c7b2541ae5ff737691547daef2e4b25f9d232eba;hp=d3eeb71b0bc20cb9da24f64b2e434182035ea3b3;hpb=ca158d7f61e340f4a4b512ce070e66c012274d79;p=csit.git diff --git a/docs/report/vpp_performance_tests/documentation/containers.rst b/docs/report/vpp_performance_tests/documentation/containers.rst index d3eeb71b0b..5ec7d9c112 100644 --- a/docs/report/vpp_performance_tests/documentation/containers.rst +++ b/docs/report/vpp_performance_tests/documentation/containers.rst @@ -1,5 +1,5 @@ -.. _containter_orchestration_in_csit: +.. _container_orchestration_in_csit: Container Orchestration in CSIT =============================== @@ -140,11 +140,8 @@ a range of virtual networking topologies. of functionality is better supported in LXC 2.1 but can be done is current version as well. -**Open Questions** - -- CSIT code is currently using cgroup to pin lxc data plane thread to - cpu cores after lxc container is created. In the future may find a - more universal way to do it. +- CSIT code is currently using cgroup to control the range of CPU cores the + LXC container runs on. VPP thread pinning is defined vpp startup.conf. Docker ~~~~~~ @@ -166,7 +163,6 @@ containerized applications used in CSIT performance tests. configuration file controls the range of CPU cores the Docker image must run on. VPP thread pinning defined vpp startup.conf. - Kubernetes ~~~~~~~~~~ @@ -180,15 +176,6 @@ K8s pod definitions including compute resource allocation is provided in CSIT uses K8s and its infrastructure components like etcd to control all phases of container based virtualized network topologies. -**Known Issues** - -- Unable to properly pin k8s pods and containers to cpu cores. This will be - addressed in Kubernetes 1.8+ in alpha testing. - -**Open Questions** - -- Clarify the functions provided by Contiv and Calico in Ligato system? - Ligato ~~~~~~ @@ -198,10 +185,8 @@ using goVPP [govpp]_ and vpp-agent [vpp-agent]_. **Known Issues** -**Open Questions** - - Currently using a separate LF Jenkins job for building csit-centric - vpp_agent docker images vs. dockerhub/ligato ones. + prod_vpp_agent docker images vs. dockerhub/ligato ones. Implementation -------------- @@ -286,9 +271,6 @@ Current CSIT implementation is illustrated using UML Class diagram: Sequentional diagram that illustrates the creation of a single container. -.. mk: what "RF KW" is meant below? -.. mk: the flow sequence should adhere to the lifecycle events listed earlier in this doc. - :: Legend: @@ -415,7 +397,7 @@ Kubernetes is implemented as separate library ``KubernetesUtils.py``, with a class with the same name. This utility provides an API for L2 Robot Keywords to control ``kubectl`` installed on each of DUTs. One time initialization script, ``resources/libraries/bash/k8s_setup.sh`` -does reset/init kubectl, applies Calico v2.4.1 and initializes the +does reset/init kubectl, applies Calico v2.6.3 and initializes the ``csit`` namespace. CSIT namespace is required to not to interfere with existing setups and it further simplifies apply/get/delete Pod/ConfigMap operations on SUTs. @@ -475,10 +457,12 @@ We created separate sets of Jenkins jobs, that will be executing following: 1. Clone latest CSIT and Ligato repositaries. 2. Pull specific version of ``dev_vpp_agent`` image from Dockerhub. -3. Build ``prod_vpp_image`` Docker image from ``dev_vpp_agent`` image. -4. Shrink image using ``docker/dev_vpp_agent/shrink.sh`` script. -5. Transfer ``prod_vpp_agent_shrink`` image to DUTs. -6. Execute subset of performance tests designed for Ligato testing. +3. Extract VPP API (from ``.deb`` package) and copy into ``dev_vpp_agent`` + image +4. Rebuild vpp-agent and extract outside image. +5. Build ``prod_vpp_image`` Docker image from ``dev_vpp_agent`` image. +6. Transfer ``prod_vpp_agent`` image to DUTs. +7. Execute subset of performance tests designed for Ligato testing. :: @@ -491,7 +475,7 @@ We created separate sets of Jenkins jobs, that will be executing following: | ligato/dev_vpp_agent <------| Pull this image from +------------------------^----------------------+ | Dockerhub ligato/dev_vpp_agent: | - | Extract agent.tar.gz from dev_vpp_agent + | Rebuild and extract agent.tar.gz from dev_vpp_agent +------------------------+----------------------+ | prod_vpp_agent <------| Build by passing own +-----------------------------------------------+ | vpp.tar.gz (from nexus @@ -505,10 +489,8 @@ Approximate size of vnf-agent docker images: :: REPOSITORY TAG IMAGE ID CREATED SIZE - dev_vpp_agent latest 442771972e4a 8 hours ago 3.57 GB - dev_vpp_agent_shrink latest bd2e76980236 8 hours ago 1.68 GB - prod_vpp_agent latest e33a5551b504 2 days ago 404 MB - prod_vpp_agent_shrink latest 446b271cce26 2 days ago 257 MB + dev-vpp-agent latest 78c53bd57e2 6 weeks ago 9.79GB + prod_vpp_agent latest f68af5afe601 5 weeks ago 443MB In CSIT we need to create separate performance suite under ``tests/kubernetes/perf`` which contains modified Suite setup in comparison @@ -522,7 +504,7 @@ Listed CSIT container networking test topologies are defined with DUT containerized VPP switch forwarding packets between NF containers. Each NF container runs their own instance of VPP in L2XC configuration. -Following container networking topologies are tested in CSIT |release|: +Following container networking topologies are tested in |csit-release|: - LXC topologies: @@ -535,14 +517,19 @@ Following container networking topologies are tested in CSIT |release|: - Kubernetes/Ligato topologies: - - eth-1drcl2xcbase-eth-2memif-1drcl2xc. - - eth-1drcl2xcbase-eth-4memif-2drcl2xc. - - eth-1drcl2bdbasemaclrn-eth-2memif-1drcl2xc. - - eth-1drcl2bdbasemaclrn-eth-4memif-2drcl2xc. - + - eth-1drcl2bdbasemaclrn-eth-2memif-1drcl2xc-1paral + - eth-1drcl2bdbasemaclrn-eth-2memif-2drcl2xc-1horiz + - eth-1drcl2bdbasemaclrn-eth-2memif-4drcl2xc-1horiz + - eth-1drcl2bdbasemaclrn-eth-4memif-2drcl2xc-1chain + - eth-1drcl2bdbasemaclrn-eth-8memif-4drcl2xc-1chain + - eth-1drcl2xcbase-eth-2memif-1drcl2xc-1paral + - eth-1drcl2xcbase-eth-2memif-2drcl2xc-1horiz + - eth-1drcl2xcbase-eth-2memif-4drcl2xc-1horiz + - eth-1drcl2xcbase-eth-4memif-2drcl2xc-1chain + - eth-1drcl2xcbase-eth-8memif-4drcl2xc-1chain References ----------- +~~~~~~~~~~ .. [lxc] `Linux Containers `_ .. [lxc-namespace] `Resource management: Linux kernel Namespaces and cgroups `_.