...
The automatic deployment script provided by IEC uses calico CNI by default. To enable Contiv-VPP network solution for Kubernetes, you need to make some minor modifications. In addition, the deployment methods of IEC type1 and type2 are slightly different. IEC provide details on how to install Kubernetes with Contiv-VPP networking on one or more bare-metal servers. Please refer to the contiv-vpp_setup.rst document.
IEC Type1 Specifics
| Item | Name | Description |
|---|---|---|
| 1 | Setting up MACCHIATObin | Prerequisites: IEC provide detail document to instruduce how to setup MACCHIATObin. Its contents include：Build and Update Bootloader，Setting U-Boot parameters，Kernel compilation and update. The default kernel configuration provided by Marvell does not meet the container's system requirements. A modified kernel config enable necessary module to meet container`s requirement, such as NETFILTER, IPTABLES, OVERLAY_FS, VHOST, TAP and other related kernel modules. |
| 2 | MUSDK Introduction | MUSDK version used: musdk-armada-18.09 Marvell User-Space SDK(MUSDK) is a light-weight user-space I/O driver for Marvell's Embedded Networking SoC's, Following kernel modules from MUSDK must be loaded for VPP to work:
|
| 3 | Contiv-VPP usage | A section of the document contiv-vpp_setup.rst describes how to run contivpp in type1. |
Notes
IEC type1 device is suitable for low power device.Now we choose MACCHIATObin board as the main hardware platform，but contiv-vpp master version does not support running on this board。IEC team develops new features based on v3.2.1 version that make Contiv-VPP enable on MACCHIATObin board.This feature involves the code changes of fd.io /VPP, ligato/vpp-agent,contiv/ VPP, and we will submit the relevant modifications to the community later.
IEC Type1 Specifics
...
Foundation Improvement
Use Case
...