Project Technical Lead: Georg Kunz. Elected 1/17/19.
Project Committer Details:
Initial Committers for a project will be specified at project creation. Committers have the right to commit code to the source code management system for that project.
A Contributor may be promoted to a Committer by the project’s Committers after demonstrating a history of contributions to that project.
Candidates for the project’s Project Technical Leader will be derived from the Committers of the Project. Candidates must self nominate by marking "Y" in the Self Nominate column below by Jan. 16th. Voting will take place January 17th.
Only Committers for a project are eligible to vote for a project’s Project Technical Lead.
Please see Akraino Technical Community Document section 3.1.3 for more detailed information.
Committer | Committer Company | Committer Contact Info | Committer Bio | Committer Picture | Self Nominate for PTL (Y/N) |
Andrew Wilkinson | Ericsson | N | |||
| Georg Kunz | Ericsson | georg.kunz@ericsson.com | Georg is a Senior Systems Designer at Ericsson, working mainly on SDN and NFV, and an active member of the OPNFV and OpenStack communities. Georg is a member of the OPNFV TSC and a former PTL of the OPNFV NetReady and Dovetail projects. He contributes to the OPNFV Verified compliance program and the OPNFV testing community. Moreover, he has been a contributor to the OpenStack Gluon project and the OpenStack Interop working group. In previous roles, he worked on designing and prototyping SDN solutions for 5G networks as well as integrating Openstack-based cloud infrastructures, particularly specializing in storage solutions. |
| Y |
Use Case Details:
Feature project proposers: Ericsson, Nokia and Radysis (confirm) and (others - confirm).
The following BP proposals require support of OVS-DPDK in Airship:
Network Cloud : OVS-DPDK Unicycle Dell Blueprint Proposal
Radio Edge Cloud
Edge Video Processing
(any other dependent BPs?)
Initial list of high-level working items
The table below provides a list of high-level work items required to enable support for OVS-DPDK in Airship. This list is not considered to be complete but a starting point for design discussions in the feature project. Please feel free to add / modify / extend work items.
| Task name | Description | Airship component | Implementation | Upstream reference |
|---|---|---|---|---|
| create openvswitch agent chart | create helm chart for openvswitch agent | openstack-helm | in place and being deployed when OVS is enabled | |
| create ovs-dpdk chart | create helm chart for openvswitch dpdk container | openstack-helm | Extend existing openvswitch chart with config parameters for DPDK. | https://review.openstack.org/#/c/626894/ |
| deploy neutron openvswitch agent | ensure chart of openvswitch agent is deployed | treasuremap | In place and being deployed when OVS is enabled | |
| DPDK host config: enable 1G hugepages | modify kernel cmdline to enable 1G hugepages (hugepagez=1G hugepages=8 iommu=pt intel_iommu=on ) | drydock | Already available: Define the number of available hugepages in the node's HardwareProfile: Define the kernel paramters for enabling hgepages in the node's BaremetalNode configuration (kernel_param section): | https://storyboard.openstack.org/#!/story/2004790 |
| DPDK host config: mount hugepages | mount hugepages into local file system on system boot (hardcoded mount point) | Divingbell | Two alternatives available:
Issue: does not allow fine-grained control of mount-options (e.g. specify the size of the hugepages if there are multiple available)
| https://storyboard.openstack.org/#!/story/2004790 |
| DPDK host config: make hugepage mount point a config option | make mount point config option for e.g. use by helm charts | openstack-helm | config option of helm chart (see patchset). Need to figure out how to pass overrides to chart. | https://review.openstack.org/#/c/626894/ |
| specify PCI IDs of NICs for use by DPDK | specify in site config which PCI IDs (NICs) should be decided to DPDK | Reuse data_nic0x config option defined in HardwareProfine | https://storyboard.openstack.org/#!/story/2004790 | |
| DPDK host config: install DPDK kernel modules and tools on host OS | either install host OS dpdk package or build from source | drydock (or divingbell) | https://storyboard.openstack.org/#!/story/2004790 | |
| DPDK host config: load DPDK kernel module in host OS | load dpdk kernel modules uio and igb_uio during host boot-up | drydock (or divingbell) | https://storyboard.openstack.org/#!/story/2004790 | |
| DPDK host config: bind NICs to DPDK | use dpdk-devbind to bind specified NICs to DPDK | drydock (or divingbell) | https://storyboard.openstack.org/#!/story/2004790 | |
| hugepages is a beta feature since K8s 1.10 and enabled by default. | https://storyboard.openstack.org/#!/story/2004791 | |||
| ensure communication between OVS agent and OVS | ensure common socket configuration | openstack-helm | Already in place | |
| adapt OVS bridge configuration for OVS setup | Work items:
| openstack-helm | set and extend ml2 plugin configuration | |
| create docker image with dpdk-enabled OVS | create and host a docker image including an OVS with DPDK enabled (consider matching kernel and dpdk versions with host OS). Potential Kolla images: https://hub.docker.com/r/kolla/ubuntu-binary-ovsdpdk/ or https://hub.docker.com/r/kolla/ubuntu-source-ovsdpdk/ | kolla or loci | ||
| update site configuration to deploy ovs-dpdk | create a site configuration which actually deploys ovs-dpdk as data plane | treasuremap |
Legend:
| done / available |
| ongoing |
| blocking |