From: "O'Driscoll, Tim" <email@example.com> To: "firstname.lastname@example.org" <email@example.com> Cc: "Stokes, Ian" <firstname.lastname@example.org> Subject: [dpdk-ci] OVS Testing in DPDK Community Lab Date: Thu, 24 Jan 2019 16:38:04 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB782F7CC@IRSMSX108.ger.corp.intel.com> (raw) At our last DPDK lab meeting we discussed the proposal to add OVS testing to our community lab. Ian Stokes from our OVS team has been involved in discussions on this and provided some additional detail on the testing that the OVS project would like to use the lab for. Proposal for co-location of OVS DPDK test infrastructure with existing DPDK labs. OVS DPDK supports various hardware network devices e.g. Intel XL710, Intel 82599ES, Mellanox connectx-4, Mellanox connectx-5 etc. A problem inherent to supporting such a wide range of devices in that proposed software solutions submitted by one vendor to enable a particular feature in OVS for their particular device may impact negatively for other vendor devices, introducing performance regressions or even loss of functionality. The purpose of this lab deployment would be to provide a consolidated test bed where OVS DPDK patches could be verified using OVS DPDK unit tests and OVS DPDK functional tests to ensure no breakage/regression for all supported devices. The required infrastructure for automated patch application and testing for OVS DPDK is already available and is handled by the OVS 0-day robot. Companies involved (Initial List): Intel, Red Hat, Mellanox. (However other HW vendors may contribute HW devices in the future and also become involved) People involved: Aaron Conole from Red Hat is responsible for implementing the OVS 0-day robot and has offered to help deploy any hardware received and setup the 0 day robot on the given hardware (he is located 1 hours' drive from the existing University DPDK lab). Input from engineers in the community may also be used (Ian Stokes Intel, Ophir Munk Mellanox.) We can discuss again at our next meeting on Tuesday. Trishan has also set up a separate call with Rashid Khan to get a perspective from Red Hat, as we agreed at our last call.
reply index Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publically to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=26FA93C7ED1EAA44AB77D62FBE1D27BAB782F7CC@IRSMSX108.ger.corp.intel.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
DPDK CI discussions Archives are clonable: git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \ firstname.lastname@example.org public-inbox-index ci Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.ci AGPL code for this site: git clone https://public-inbox.org/ public-inbox