[dpdk-ci] [dpdk-marketing] Results are now public
Lincoln Lavoie
lylavoie at iol.unh.edu
Mon Nov 19 18:52:36 CET 2018
Hi Jill,
Nope, that is Marion (in the hallway) and Michayla (our assistant director)
in the machine room.
I'll work with Mara to pull up a second picture of servers, etc.
Cheers,
Lincoln
On Mon, Nov 19, 2018 at 12:49 PM Jill Lovato <jlovato at linuxfoundation.org>
wrote:
> Thank you, Mara.
>
> Couldn't help but notice in the picture that the girl inside the lab looks
> an awful lot like the girl walking in the hallway - was this just a
> coincidence, or has the photo been altered? Either way, can we get a second
> image to add to the post, maybe a closer shot of the servers themselves?
>
> Thanks!
> Jill
>
> On Mon, Nov 19, 2018 at 7:08 AM Mara Bernazzani <mbernazzani at iol.unh.edu>
> wrote:
>
>> Hello Jill,
>>
>> I apologize for the delay in getting back to you - attached is a picture
>> you can use for the blog post. Let me know when its live and we will also
>> share on our end.
>>
>> Thanks!
>> Mara
>>
>> On Fri, Nov 16, 2018 at 11:42 AM Jill Lovato <jlovato at linuxfoundation.org>
>> wrote:
>>
>>> Hi Lincoln,
>>>
>>> Thanks for the update. We'll plan to post the blog Monday afternoon or
>>> Tuesday morning.
>>>
>>> Have a great weekend,
>>> Jill
>>>
>>> On Thu, Nov 15, 2018 at 6:49 PM Lincoln Lavoie <lylavoie at iol.unh.edu>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Mara our marketing lead is out for a vacation this week. She's the
>>>> keeper of all the good / approved pictures of the lab. Should be able to
>>>> get you something early next week.
>>>>
>>>> Cheers,
>>>> Lincoln
>>>>
>>>> On Thu, Nov 15, 2018 at 9:29 PM Tu, Lijuan <lijuan.tu at intel.com> wrote:
>>>>
>>>>> Agree, I would like to see some photos of the lab.
>>>>> Should we add a brief introduction of contributors, this may attract
>>>>> more companies or individual to contribute to the lab.
>>>>>
>>>>> > -----Original Message-----
>>>>> > From: ci [mailto:ci-bounces at dpdk.org] On Behalf Of O'Driscoll, Tim
>>>>> > Sent: Friday, November 16, 2018 6:14 AM
>>>>> > To: Thomas Monjalon <thomas at monjalon.net>; Jeremy Plsek
>>>>> > <jplsek at iol.unh.edu>
>>>>> > Cc: Yigit, Ferruh <ferruh.yigit at intel.com>; ci at dpdk.org;
>>>>> > marketing at dpdk.org; Lincoln Lavoie <lylavoie at iol.unh.edu>; Patrick
>>>>> > MacArthur <pmacarth at iol.unh.edu>
>>>>> > Subject: Re: [dpdk-ci] [dpdk-marketing] Results are now public
>>>>> >
>>>>> > This looks good to me too. Some pictures would be nice, perhaps a
>>>>> snapshot
>>>>> > of the dashboard some of the hardware in the lab. It would be good
>>>>> to get
>>>>> > this posted on dpdk.org, and send a note to announce at dpdk.org to let
>>>>> > people know about it.
>>>>> >
>>>>> > > -----Original Message-----
>>>>> > > From: Thomas Monjalon [mailto:thomas at monjalon.net]
>>>>> > > Sent: Wednesday, November 14, 2018 10:17 PM
>>>>> > > To: Jeremy Plsek <jplsek at iol.unh.edu>
>>>>> > > Cc: O'Driscoll, Tim <tim.odriscoll at intel.com>; Yigit, Ferruh
>>>>> > > <ferruh.yigit at intel.com>; ci at dpdk.org; marketing at dpdk.org; Lincoln
>>>>> > > Lavoie <lylavoie at iol.unh.edu>; Patrick MacArthur
>>>>> > > <pmacarth at iol.unh.edu>
>>>>> > > Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public
>>>>> > >
>>>>> > > Looks great!
>>>>> > > I think adding pictures would be nice for the blog.
>>>>> > > Thank you
>>>>> > >
>>>>> > > 14/11/2018 22:07, Jeremy Plsek:
>>>>> > > > With help from Lincoln and Patrick, below is an initial draft of
>>>>> the
>>>>> > > blog post.
>>>>> > > >
>>>>> > > >
>>>>> > > >
>>>>> > > > DPDK Community Lab Publishes Relative Performance Testing Results
>>>>> > > >
>>>>> > > > The DPDK Community Lab is an open, independent testing resource
>>>>> for
>>>>> > > > the DPDK project. Its purpose is to perform automated testing on
>>>>> > > > incoming patch submissions, to ensure the performance and
>>>>> quality of
>>>>> > > > DPDK is maintained. Participation in the lab is open to all DPDK
>>>>> > > > project participants.
>>>>> > > >
>>>>> > > > For some time now, the DPDK Community Lab has been gathering
>>>>> > > > performance deltas using the single-core packet I/O layer 2
>>>>> > > > throughput test from DTS for each patch series submitted to DPDK
>>>>> > > > compared to the master branch. We are pleased to announce that
>>>>> the
>>>>> > > > Lab has recently been allowed to make these results public. These
>>>>> > > > results are also now published to Patchwork as they are
>>>>> > > > automatically generated. These results currently contain Mellanox
>>>>> > > > and Intel devices, and the lab is able to support hardware from
>>>>> any
>>>>> > > > DPDK participants wishing to support these testing efforts.
>>>>> > > >
>>>>> > > > To view these results, you can go to DPDK Community Lab Dashboard
>>>>> > > > via the following link: https://lab.dpdk.org. The dashboard
>>>>> lists an
>>>>> > > > overview of all active patch series and their results. Detailed
>>>>> > > > results can be viewed by clicking on the patch series. If a patch
>>>>> > > > fails to merge into master, a build log will show to help
>>>>> identify
>>>>> > > > any issues. If a patch cleanly merges into master, performance
>>>>> delta
>>>>> > > > results will show for each participating member.
>>>>> > > >
>>>>> > > > The Lab is hosted by the University of New Hampshire
>>>>> > > > InterOperability Laboratory, as a neutral, third party location.
>>>>> > > > This provides a secure environment for hosting equipment and
>>>>> > > > generating unbiased results for all participating vendors. Lab
>>>>> > > > participants, i.e. companies hosting equipment in the testing,
>>>>> can
>>>>> > > > securely access their equipment through a VPN, allowing for
>>>>> > > > maintenance and performance tuning, as the DPDK project
>>>>> progresses.
>>>>> > > >
>>>>> > > > The Lab works by polling the Patchwork API. When new patches are
>>>>> > > > submitted, the CI server merges them with the master branch and
>>>>> > > > generates a tarball. Each participating system unpacks and
>>>>> installs
>>>>> > > > the DPDK tarball and then runs the performance testing against
>>>>> this
>>>>> > > > DPDK build. When all systems have finished testing, the CI
>>>>> gathers
>>>>> > > > the results into our internal database to be shown on the
>>>>> Dashboard,
>>>>> > > > and sends final reports to Patchwork to show up on the submitted
>>>>> patch.
>>>>> > > > This allows patch submitters to utilize Patchwork to view their
>>>>> > > > individual results, while also allowing anyone to quickly see an
>>>>> > > > overview of results on the Dashboard. The system provides
>>>>> > > > maintainers with positive confirmation of the stability and
>>>>> > > > performance of the overall project.
>>>>> > > >
>>>>> > > > In the future, we plan to open the Lab to more testing scenarios,
>>>>> > > > such as performance testing of other features, beyond single-core
>>>>> > > > packet I/O layer 2 throughput, and possibly running Unit Tests
>>>>> for DPDK.
>>>>> > > > Additional features will be added to the Dashboard, such as
>>>>> showing
>>>>> > > > graphs of the performance changes of master over time.
>>>>> > > >
>>>>> > > > If your company would like to be involved, email the Continuous
>>>>> > > > Integration group at ci at dpdk.org and dpdklab at iol.unh.edu.
>>>>> > > >
>>>>> > > >
>>>>> > > >
>>>>> > > > Thanks!
>>>>> > > >
>>>>> > > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek at iol.unh.edu
>>>>> >
>>>>> > > wrote:
>>>>> > > > >
>>>>> > > > > I can try to get it done later today, but I expect it to be
>>>>> more
>>>>> > > likely done on Monday.
>>>>> > > > >
>>>>> > > > > On Fri, Nov 9, 2018, 9:08 AM O'Driscoll, Tim
>>>>> > > <tim.odriscoll at intel.com wrote:
>>>>> > > > >>
>>>>> > > > >>
>>>>> > > > >>
>>>>> > > > >> > -----Original Message-----
>>>>> > > > >> > From: Thomas Monjalon [mailto:thomas at monjalon.net]
>>>>> > > > >> > Sent: Friday, November 9, 2018 2:02 PM
>>>>> > > > >> > To: O'Driscoll, Tim <tim.odriscoll at intel.com>
>>>>> > > > >> > Cc: Yigit, Ferruh <ferruh.yigit at intel.com>; Jeremy Plsek
>>>>> > > > >> > <jplsek at iol.unh.edu>; ci at dpdk.org; marketing at dpdk.org
>>>>> > > > >> > Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now
>>>>> public
>>>>> > > > >> >
>>>>> > > > >> > 09/11/2018 14:58, O'Driscoll, Tim:
>>>>> > > > >> > > From: Thomas Monjalon
>>>>> > > > >> > > > 08/11/2018 14:01, Ferruh Yigit:
>>>>> > > > >> > > > > On 11/7/2018 7:30 AM, Thomas Monjalon wrote:
>>>>> > > > >> > > > > > 06/11/2018 16:33, Jeremy Plsek:
>>>>> > > > >> > > > > >> Hi all,
>>>>> > > > >> > > > > >>
>>>>> > > > >> > > > > >> This is just an update that all detailed results
>>>>> are
>>>>> > > > >> > > > > >> now
>>>>> > > > >> > public.
>>>>> > > > >> > > > > >>
>>>>> > > > >> > > > > >> If there is anything out of place, feel free to
>>>>> let me
>>>>> > > know!
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > It is really nice!
>>>>> > > > >> > > > > > Thank you
>>>>> > > > >> > > > >
>>>>> > > > >> > > > > Should we announce this in 'announce' or 'dev' mail
>>>>> lists?
>>>>> > > Many
>>>>> > > > >> > people
>>>>> > > > >> > > > not aware
>>>>> > > > >> > > > > of this.
>>>>> > > > >> > > >
>>>>> > > > >> > > > It deserves an announce.
>>>>> > > > >> > > > And even a blog post I guess.
>>>>> > > > >> > > > +Cc marketing team
>>>>> > > > >> > >
>>>>> > > > >> > > Agreed. I can do a quick post to announce at dpdk.org. I
>>>>> believe
>>>>> > > Jeremy
>>>>> > > > >> > is working on a blog post which can provide more detail.
>>>>> > > > >> >
>>>>> > > > >> > Should we wait to have a blog post and reference it in the
>>>>> > > announce?
>>>>> > > > >>
>>>>> > > > >> Good question. I think it depends how long the blog will
>>>>> take. If
>>>>> > > we can do it fairly quickly, then this is a good idea. If it's
>>>>> going
>>>>> > > to take a few weeks, then we should announce it now.
>>>>> > > > >>
>>>>> > > > >> Jeremy: When do you think the blog will be ready?
>>>>> > > > >>
>>>>> > > >
>>>>> > > >
>>>>> > > > --
>>>>> > > > Jeremy Plsek
>>>>> > > > UNH InterOperability Laboratory
>>>>> > > >
>>>>> > >
>>>>> > >
>>>>> > >
>>>>> > >
>>>>>
>>>>>
>>>>
>>>> --
>>>>
>>>> *******************************************************************************
>>>> *Lincoln Lavoie*
>>>> Senior Engineer, Broadband Technologies
>>>>
>>>> <https://www.iol.unh.edu>
>>>> www.iol.unh.edu
>>>> 21 Madbury Rd., Ste. 100, Durham, NH 03824
>>>> Mobile: +1-603-674-2755
>>>> lylavoie at iol.unh.edu
>>>> <http://www.facebook.com/UNHIOL#> <https://twitter.com/#!/UNH_IOL>
>>>> <http://www.linkedin.com/company/unh-interoperability-lab>
>>>>
>>>> Ars sine scientia nihil est! -- Art without science is nothing.
>>>> Scientia sine ars est vacua! -- Science without art is empty.
>>>>
>>>> Broadband Forum Gfast Certified Product List
>>>> <https://www.broadband-forum.org/implementation/interop-certification/gfast-certified-products>
>>>>
>>>> *******************************************************************************
>>>>
>>>
>>>
>>> --
>>> *Jill Lovato*
>>> Senior PR Manager
>>> The Linux Foundation
>>> jlovato at linuxfoundation.org
>>> Skype: jill.lovato1
>>> Phone: +1.503.703.8268
>>>
>>
>>
>> --
>> Mara Bernazzani
>> Communications Coordinator
>> UNH InterOperability Laboratory
>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>> mbernazzani at iol.unh.edu
>> 1-603-862-0901 (o)
>> [image: IOL Twitter] <https://twitter.com/UNH_IOL> [image: IOL LinkedIn]
>> <https://www.linkedin.com/company-beta/7252> [image: IOL Facebook]
>> <https://www.facebook.com/UNHIOL/>
>>
>> Interested to learn more? Sign up <http://bit.ly/1XNuJLV> for our
>> quarterly newsletter for industry news and IOL happenings.
>>
>
>
> --
> *Jill Lovato*
> Senior PR Manager
> The Linux Foundation
> jlovato at linuxfoundation.org
> Skype: jill.lovato1
> Phone: +1.503.703.8268
>
--
*******************************************************************************
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies
<https://www.iol.unh.edu>
www.iol.unh.edu
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
lylavoie at iol.unh.edu
<http://www.facebook.com/UNHIOL#> <https://twitter.com/#!/UNH_IOL>
<http://www.linkedin.com/company/unh-interoperability-lab>
Ars sine scientia nihil est! -- Art without science is nothing.
Scientia sine ars est vacua! -- Science without art is empty.
Broadband Forum Gfast Certified Product List
<https://www.broadband-forum.org/implementation/interop-certification/gfast-certified-products>
*******************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mails.dpdk.org/archives/ci/attachments/20181119/d7ce232c/attachment-0001.html>
More information about the ci
mailing list