summaryrefslogtreecommitdiffstats
path: root/build/ovs-dpdk-preconfig.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-08-04Add support for nosdn-ovs-dpdk scenarioFeng Pan1-6/+6
Change-Id: I31fca214b7d16cecc261137567fa7ecf63abfe04 Signed-off-by: Feng Pan <fpan@redhat.com>
2017-05-10Adding yamllint to build checksDan Radez1-6/+10
- making formatting changes to yaml files to meet yamllint checks Change-Id: Id48a8446512943e908e61dc00bbe6c033af27775 Signed-off-by: Dan Radez <dradez@redhat.com>
2017-04-28Fixes bugs in ovs dpdkTim Rozet1-2/+2
Changes Include: - Fixes an issue where using non-1st nic admin network deployment would result in loss of network connectivity during deployment. - Fixes an issue where not specifying cores to pin to in performance options would result in an incorrect '0' value used for core mask. JIRA: APEX-452 JIRA: APEX-453 Change-Id: I413290161abd9b2fa39b659d5ff989da9554f603 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-03-24Fixes OVS DPDK scenariosTim Rozet1-0/+101
This fixes nosdn OVS DPDK scenarios to work with OVS 2.6. It also adds support for the ODL DPDK scenario. OVS DPDK configuration is done during preconfig on compute nodes. All nodes make use of first boot script to get kernel params like hugepages. The network settings are modified to use real nic names for the virtual network settings file. This is required due to a timing bug with os-net-config and using first-boot script. The network settings file also contains the UIO driver to use with DPDK. JIRA: APEX-314 opnfv-tht-pr: 117 Change-Id: I46b6fca71ecec38981968133ba2411f64d7c6445 Signed-off-by: Tim Rozet <trozet@redhat.com>