[dpdk-ci] Results are now public

[dpdk-ci] Results are now public

[Jeremy Plsek]

[-- Attachment #1: Type: text/plain, Size: 193 bytes --]

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!

Thanks
-- 
Jeremy Plsek
UNH InterOperability Laboratory

[-- Attachment #2: Type: text/html, Size: 571 bytes --]

Re: [dpdk-ci] Results are now public

[Thomas Monjalon]

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

Re: [dpdk-ci] Results are now public

[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.

Re: [dpdk-ci] Results are now public

[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

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Trishan de Lanerolle]

[-- Attachment #1: Type: text/plain, Size: 878 bytes --]

Jeremy,

Would you like to take a first pass at a blog post. We can help edit it and
put it up on the site.

Thomas/Ferruh,
Can you update core.dpdk.org page on the performance lab to include a link
to the new dashboard and perhaps a short primer to go with it.

Trishan




On Thu, Nov 8, 2018, 8:10 AM Thomas Monjalon <thomas@monjalon.net wrote:

> 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
>
>
>

[-- Attachment #2: Type: text/html, Size: 1535 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Thomas Monjalon]

08/11/2018 14:16, Trishan de Lanerolle:
> Thomas/Ferruh,
> Can you update core.dpdk.org page on the performance lab to include a link
> to the new dashboard and perhaps a short primer to go with it.

Yes we are already working on it.
Ali sent a patch, and we are discussing the name of the lab.

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Jeremy Plsek]

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

Sure, I can look into creating a draft.

On Thu, Nov 8, 2018 at 8:16 AM Trishan de Lanerolle <
tdelanerolle@linuxfoundation.org> wrote:

> Jeremy,
>
> Would you like to take a first pass at a blog post. We can help edit it
> and put it up on the site.
>
> Thomas/Ferruh,
> Can you update core.dpdk.org page on the performance lab to include a
> link to the new dashboard and perhaps a short primer to go with it.
>
> Trishan
>
>
>
>
> On Thu, Nov 8, 2018, 8:10 AM Thomas Monjalon <thomas@monjalon.net wrote:
>
>> 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
>>
>>
>>

-- 
Jeremy Plsek
UNH InterOperability Laboratory

[-- Attachment #2: Type: text/html, Size: 2288 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[O'Driscoll, Tim]

> -----Original Message-----
> From: marketing [mailto:marketing-bounces@dpdk.org] On Behalf Of Thomas
> Monjalon
> Sent: Thursday, November 8, 2018 1:10 PM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>
> Cc: Jeremy Plsek <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@dpdk.org
> Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public
> 
> 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@dpdk.org. I believe Jeremy is working on a blog post which can provide more detail.

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Thomas Monjalon]

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@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?

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Trishan de Lanerolle]

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

Let's coordinate the blog post and announcement. I think we can go ahead
and update the webpage as a first step.
Trishan


On Fri, Nov 9, 2018, 9:01 AM Thomas Monjalon <thomas@monjalon.net wrote:

> 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@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?
>
>
>

[-- Attachment #2: Type: text/html, Size: 1743 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[O'Driscoll, Tim]

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Friday, November 9, 2018 2:02 PM
> To: O'Driscoll, Tim <tim.odriscoll@intel.com>
> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
> <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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?

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Jeremy Plsek]

[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]

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@intel.com wrote:

>
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > Sent: Friday, November 9, 2018 2:02 PM
> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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?
>
>

[-- Attachment #2: Type: text/html, Size: 2973 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[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@dpdk.org and dpdklab@iol.unh.edu.



Thanks!

On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@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@intel.com wrote:
>>
>>
>>
>> > -----Original Message-----
>> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
>> > Sent: Friday, November 9, 2018 2:02 PM
>> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
>> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
>> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Thomas Monjalon]

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@dpdk.org and dpdklab@iol.unh.edu.
> 
> 
> 
> Thanks!
> 
> On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@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@intel.com wrote:
> >>
> >>
> >>
> >> > -----Original Message-----
> >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> >> > Sent: Friday, November 9, 2018 2:02 PM
> >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
> >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
> >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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
> 

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[O'Driscoll, Tim]

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@dpdk.org to let people know about it.

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Wednesday, November 14, 2018 10:17 PM
> To: Jeremy Plsek <jplsek@iol.unh.edu>
> Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh
> <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; Lincoln
> Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur <pmacarth@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@dpdk.org and dpdklab@iol.unh.edu.
> >
> >
> >
> > Thanks!
> >
> > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@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@intel.com wrote:
> > >>
> > >>
> > >>
> > >> > -----Original Message-----
> > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > >> > Sent: Friday, November 9, 2018 2:02 PM
> > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
> > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
> > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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
> >
> 
> 
> 
> 

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Jill Lovato]

[-- Attachment #1: Type: text/plain, Size: 7118 bytes --]

Agree on the draft - thank you, Jeremy, for putting this together!

I haven't seen any photos of the lab - can someone point me in the right
direction, or perhaps snap and few and share on this thread? I can get this
posted to the DPDK site as early as tomorrow (Friday) morning.

Many thanks,
Jill

On Thu, Nov 15, 2018 at 2:13 PM O'Driscoll, Tim <tim.odriscoll@intel.com>
wrote:

> 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@dpdk.org to let
> people know about it.
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > Sent: Wednesday, November 14, 2018 10:17 PM
> > To: Jeremy Plsek <jplsek@iol.unh.edu>
> > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh
> > <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; Lincoln
> > Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur <pmacarth@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@dpdk.org and dpdklab@iol.unh.edu.
> > >
> > >
> > >
> > > Thanks!
> > >
> > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@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@intel.com wrote:
> > > >>
> > > >>
> > > >>
> > > >> > -----Original Message-----
> > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > >> > Sent: Friday, November 9, 2018 2:02 PM
> > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
> > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
> > > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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
> > >
> >
> >
> >
> >
>
>

-- 
*Jill Lovato*
Senior PR Manager
The Linux Foundation
jlovato@linuxfoundation.org
Skype: jill.lovato1
Phone: +1.503.703.8268

[-- Attachment #2: Type: text/html, Size: 11102 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Tu, Lijuan]

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@dpdk.org] On Behalf Of O'Driscoll, Tim
> Sent: Friday, November 16, 2018 6:14 AM
> To: Thomas Monjalon <thomas@monjalon.net>; Jeremy Plsek
> <jplsek@iol.unh.edu>
> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; ci@dpdk.org;
> marketing@dpdk.org; Lincoln Lavoie <lylavoie@iol.unh.edu>; Patrick
> MacArthur <pmacarth@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@dpdk.org to let
> people know about it.
> 
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > Sent: Wednesday, November 14, 2018 10:17 PM
> > To: Jeremy Plsek <jplsek@iol.unh.edu>
> > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh
> > <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; Lincoln
> > Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur
> > <pmacarth@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@dpdk.org and dpdklab@iol.unh.edu.
> > >
> > >
> > >
> > > Thanks!
> > >
> > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@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@intel.com wrote:
> > > >>
> > > >>
> > > >>
> > > >> > -----Original Message-----
> > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > >> > Sent: Friday, November 9, 2018 2:02 PM
> > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
> > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
> > > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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
> > >
> >
> >
> >
> >

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Lincoln Lavoie]

[-- Attachment #1: Type: text/plain, Size: 8626 bytes --]

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@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@dpdk.org] On Behalf Of O'Driscoll, Tim
> > Sent: Friday, November 16, 2018 6:14 AM
> > To: Thomas Monjalon <thomas@monjalon.net>; Jeremy Plsek
> > <jplsek@iol.unh.edu>
> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; ci@dpdk.org;
> > marketing@dpdk.org; Lincoln Lavoie <lylavoie@iol.unh.edu>; Patrick
> > MacArthur <pmacarth@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@dpdk.org to let
> > people know about it.
> >
> > > -----Original Message-----
> > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > Sent: Wednesday, November 14, 2018 10:17 PM
> > > To: Jeremy Plsek <jplsek@iol.unh.edu>
> > > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh
> > > <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; Lincoln
> > > Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur
> > > <pmacarth@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@dpdk.org and dpdklab@iol.unh.edu.
> > > >
> > > >
> > > >
> > > > Thanks!
> > > >
> > > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@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@intel.com wrote:
> > > > >>
> > > > >>
> > > > >>
> > > > >> > -----Original Message-----
> > > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > > >> > Sent: Friday, November 9, 2018 2:02 PM
> > > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
> > > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
> > > > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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@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>
*******************************************************************************

[-- Attachment #2: Type: text/html, Size: 14748 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Jill Lovato]

[-- Attachment #1: Type: text/plain, Size: 9208 bytes --]

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@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@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@dpdk.org] On Behalf Of O'Driscoll, Tim
>> > Sent: Friday, November 16, 2018 6:14 AM
>> > To: Thomas Monjalon <thomas@monjalon.net>; Jeremy Plsek
>> > <jplsek@iol.unh.edu>
>> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; ci@dpdk.org;
>> > marketing@dpdk.org; Lincoln Lavoie <lylavoie@iol.unh.edu>; Patrick
>> > MacArthur <pmacarth@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@dpdk.org to let
>> > people know about it.
>> >
>> > > -----Original Message-----
>> > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
>> > > Sent: Wednesday, November 14, 2018 10:17 PM
>> > > To: Jeremy Plsek <jplsek@iol.unh.edu>
>> > > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh
>> > > <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; Lincoln
>> > > Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur
>> > > <pmacarth@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@dpdk.org and dpdklab@iol.unh.edu.
>> > > >
>> > > >
>> > > >
>> > > > Thanks!
>> > > >
>> > > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@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@intel.com wrote:
>> > > > >>
>> > > > >>
>> > > > >>
>> > > > >> > -----Original Message-----
>> > > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
>> > > > >> > Sent: Friday, November 9, 2018 2:02 PM
>> > > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
>> > > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
>> > > > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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@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@linuxfoundation.org
Skype: jill.lovato1
Phone: +1.503.703.8268

[-- Attachment #2: Type: text/html, Size: 15913 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Mara Bernazzani]

[-- Attachment #1.1: Type: text/plain, Size: 10222 bytes --]

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@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@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@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@dpdk.org] On Behalf Of O'Driscoll, Tim
>>> > Sent: Friday, November 16, 2018 6:14 AM
>>> > To: Thomas Monjalon <thomas@monjalon.net>; Jeremy Plsek
>>> > <jplsek@iol.unh.edu>
>>> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; ci@dpdk.org;
>>> > marketing@dpdk.org; Lincoln Lavoie <lylavoie@iol.unh.edu>; Patrick
>>> > MacArthur <pmacarth@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@dpdk.org to let
>>> > people know about it.
>>> >
>>> > > -----Original Message-----
>>> > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
>>> > > Sent: Wednesday, November 14, 2018 10:17 PM
>>> > > To: Jeremy Plsek <jplsek@iol.unh.edu>
>>> > > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh
>>> > > <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; Lincoln
>>> > > Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur
>>> > > <pmacarth@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@dpdk.org and dpdklab@iol.unh.edu.
>>> > > >
>>> > > >
>>> > > >
>>> > > > Thanks!
>>> > > >
>>> > > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@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@intel.com wrote:
>>> > > > >>
>>> > > > >>
>>> > > > >>
>>> > > > >> > -----Original Message-----
>>> > > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
>>> > > > >> > Sent: Friday, November 9, 2018 2:02 PM
>>> > > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
>>> > > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
>>> > > > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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@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@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@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.

[-- Attachment #1.2: Type: text/html, Size: 18327 bytes --]

[-- Attachment #2: Racks_From outside.jpg --]
[-- Type: image/jpeg, Size: 5656872 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Jill Lovato]

[-- Attachment #1: Type: text/plain, Size: 11080 bytes --]

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@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@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@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@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@dpdk.org] On Behalf Of O'Driscoll, Tim
>>>> > Sent: Friday, November 16, 2018 6:14 AM
>>>> > To: Thomas Monjalon <thomas@monjalon.net>; Jeremy Plsek
>>>> > <jplsek@iol.unh.edu>
>>>> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; ci@dpdk.org;
>>>> > marketing@dpdk.org; Lincoln Lavoie <lylavoie@iol.unh.edu>; Patrick
>>>> > MacArthur <pmacarth@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@dpdk.org to let
>>>> > people know about it.
>>>> >
>>>> > > -----Original Message-----
>>>> > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
>>>> > > Sent: Wednesday, November 14, 2018 10:17 PM
>>>> > > To: Jeremy Plsek <jplsek@iol.unh.edu>
>>>> > > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh
>>>> > > <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; Lincoln
>>>> > > Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur
>>>> > > <pmacarth@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@dpdk.org and dpdklab@iol.unh.edu.
>>>> > > >
>>>> > > >
>>>> > > >
>>>> > > > Thanks!
>>>> > > >
>>>> > > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@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@intel.com wrote:
>>>> > > > >>
>>>> > > > >>
>>>> > > > >>
>>>> > > > >> > -----Original Message-----
>>>> > > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
>>>> > > > >> > Sent: Friday, November 9, 2018 2:02 PM
>>>> > > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
>>>> > > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
>>>> > > > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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@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@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@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@linuxfoundation.org
Skype: jill.lovato1
Phone: +1.503.703.8268

[-- Attachment #2: Type: text/html, Size: 19627 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Lincoln Lavoie]

[-- Attachment #1: Type: text/plain, Size: 12466 bytes --]

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@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@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@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@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@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@dpdk.org] On Behalf Of O'Driscoll, Tim
>>>>> > Sent: Friday, November 16, 2018 6:14 AM
>>>>> > To: Thomas Monjalon <thomas@monjalon.net>; Jeremy Plsek
>>>>> > <jplsek@iol.unh.edu>
>>>>> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; ci@dpdk.org;
>>>>> > marketing@dpdk.org; Lincoln Lavoie <lylavoie@iol.unh.edu>; Patrick
>>>>> > MacArthur <pmacarth@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@dpdk.org to let
>>>>> > people know about it.
>>>>> >
>>>>> > > -----Original Message-----
>>>>> > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
>>>>> > > Sent: Wednesday, November 14, 2018 10:17 PM
>>>>> > > To: Jeremy Plsek <jplsek@iol.unh.edu>
>>>>> > > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh
>>>>> > > <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; Lincoln
>>>>> > > Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur
>>>>> > > <pmacarth@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@dpdk.org and dpdklab@iol.unh.edu.
>>>>> > > >
>>>>> > > >
>>>>> > > >
>>>>> > > > Thanks!
>>>>> > > >
>>>>> > > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@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@intel.com wrote:
>>>>> > > > >>
>>>>> > > > >>
>>>>> > > > >>
>>>>> > > > >> > -----Original Message-----
>>>>> > > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
>>>>> > > > >> > Sent: Friday, November 9, 2018 2:02 PM
>>>>> > > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
>>>>> > > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
>>>>> > > > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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@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@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@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@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@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>
*******************************************************************************

[-- Attachment #2: Type: text/html, Size: 22798 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Jill Lovato]

[-- Attachment #1: Type: text/plain, Size: 13292 bytes --]

Awesome! Thank you!

The blog is live:
https://www.dpdk.org/blog/2018/11/19/dpdk-community-lab-publishes-relative-performance-testing-results/

We'll update with the second image.

On Mon, Nov 19, 2018 at 9:52 AM Lincoln Lavoie <lylavoie@iol.unh.edu> wrote:

> 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@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@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@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@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@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@dpdk.org] On Behalf Of O'Driscoll, Tim
>>>>>> > Sent: Friday, November 16, 2018 6:14 AM
>>>>>> > To: Thomas Monjalon <thomas@monjalon.net>; Jeremy Plsek
>>>>>> > <jplsek@iol.unh.edu>
>>>>>> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; ci@dpdk.org;
>>>>>> > marketing@dpdk.org; Lincoln Lavoie <lylavoie@iol.unh.edu>; Patrick
>>>>>> > MacArthur <pmacarth@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@dpdk.org to
>>>>>> let
>>>>>> > people know about it.
>>>>>> >
>>>>>> > > -----Original Message-----
>>>>>> > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
>>>>>> > > Sent: Wednesday, November 14, 2018 10:17 PM
>>>>>> > > To: Jeremy Plsek <jplsek@iol.unh.edu>
>>>>>> > > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh
>>>>>> > > <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org;
>>>>>> Lincoln
>>>>>> > > Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur
>>>>>> > > <pmacarth@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@dpdk.org and dpdklab@iol.unh.edu.
>>>>>> > > >
>>>>>> > > >
>>>>>> > > >
>>>>>> > > > Thanks!
>>>>>> > > >
>>>>>> > > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <
>>>>>> jplsek@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@intel.com wrote:
>>>>>> > > > >>
>>>>>> > > > >>
>>>>>> > > > >>
>>>>>> > > > >> > -----Original Message-----
>>>>>> > > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
>>>>>> > > > >> > Sent: Friday, November 9, 2018 2:02 PM
>>>>>> > > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
>>>>>> > > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
>>>>>> > > > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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@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@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@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@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@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@linuxfoundation.org
Skype: jill.lovato1
Phone: +1.503.703.8268

[-- Attachment #2: Type: text/html, Size: 24232 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Thomas Monjalon]

Hi,

The page for the lab has changed from
	http://core.dpdk.org/perf-lab/
to
	http://core.dpdk.org/lab/

There is a redirect, but please could you update the blog post with the new URL?

Thank you


19/11/2018 18:55, Jill Lovato:
> Awesome! Thank you!
> 
> The blog is live:
> https://www.dpdk.org/blog/2018/11/19/dpdk-community-lab-publishes-relative-performance-testing-results/

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[O'Driscoll, Tim]

[-- Attachment #1: Type: text/plain, Size: 14484 bytes --]

That’s great. I think there should be a post to the announce@dpdk.org<mailto:announce@dpdk.org> list to draw attention to this.

Jeremy: Do you want to send this, since you and the UNH team did a lot of the work to get it set up?

From: Jill Lovato [mailto:jlovato@linuxfoundation.org]
Sent: Monday, November 19, 2018 5:55 PM
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: Mara Bernazzani <mbernazzani@iol.unh.edu>; Tu, Lijuan <lijuan.tu@intel.com>; O'Driscoll, Tim <tim.odriscoll@intel.com>; Thomas Monjalon <thomas@monjalon.net>; jplsek@iol.unh.edu; Yigit, Ferruh <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; pmacarth@iol.unh.edu
Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public

Awesome! Thank you!

The blog is live: https://www.dpdk.org/blog/2018/11/19/dpdk-community-lab-publishes-relative-performance-testing-results/

We'll update with the second image.

On Mon, Nov 19, 2018 at 9:52 AM Lincoln Lavoie <lylavoie@iol.unh.edu<mailto:lylavoie@iol.unh.edu>> wrote:
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@linuxfoundation.org<mailto:jlovato@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@iol.unh.edu<mailto:mbernazzani@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@linuxfoundation.org<mailto:jlovato@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@iol.unh.edu<mailto:lylavoie@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@intel.com<mailto:lijuan.tu@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@dpdk.org<mailto:ci-bounces@dpdk.org>] On Behalf Of O'Driscoll, Tim
> Sent: Friday, November 16, 2018 6:14 AM
> To: Thomas Monjalon <thomas@monjalon.net<mailto:thomas@monjalon.net>>; Jeremy Plsek
> <jplsek@iol.unh.edu<mailto:jplsek@iol.unh.edu>>
> Cc: Yigit, Ferruh <ferruh.yigit@intel.com<mailto:ferruh.yigit@intel.com>>; ci@dpdk.org<mailto:ci@dpdk.org>;
> marketing@dpdk.org<mailto:marketing@dpdk.org>; Lincoln Lavoie <lylavoie@iol.unh.edu<mailto:lylavoie@iol.unh.edu>>; Patrick
> MacArthur <pmacarth@iol.unh.edu<mailto:pmacarth@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<http://dpdk.org>, and send a note to announce@dpdk.org<mailto:announce@dpdk.org> to let
> people know about it.
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas@monjalon.net<mailto:thomas@monjalon.net>]
> > Sent: Wednesday, November 14, 2018 10:17 PM
> > To: Jeremy Plsek <jplsek@iol.unh.edu<mailto:jplsek@iol.unh.edu>>
> > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com<mailto:tim.odriscoll@intel.com>>; Yigit, Ferruh
> > <ferruh.yigit@intel.com<mailto:ferruh.yigit@intel.com>>; ci@dpdk.org<mailto:ci@dpdk.org>; marketing@dpdk.org<mailto:marketing@dpdk.org>; Lincoln
> > Lavoie <lylavoie@iol.unh.edu<mailto:lylavoie@iol.unh.edu>>; Patrick MacArthur
> > <pmacarth@iol.unh.edu<mailto:pmacarth@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@dpdk.org<mailto:ci@dpdk.org> and dpdklab@iol.unh.edu<mailto:dpdklab@iol.unh.edu>.
> > >
> > >
> > >
> > > Thanks!
> > >
> > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@iol.unh.edu<mailto:jplsek@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@intel.com<mailto:tim.odriscoll@intel.com> wrote:
> > > >>
> > > >>
> > > >>
> > > >> > -----Original Message-----
> > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net<mailto:thomas@monjalon.net>]
> > > >> > Sent: Friday, November 9, 2018 2:02 PM
> > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com<mailto:tim.odriscoll@intel.com>>
> > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com<mailto:ferruh.yigit@intel.com>>; Jeremy Plsek
> > > >> > <jplsek@iol.unh.edu<mailto:jplsek@iol.unh.edu>>; ci@dpdk.org<mailto:ci@dpdk.org>; marketing@dpdk.org<mailto:marketing@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@dpdk.org<mailto:announce@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<https://www.iol.unh.edu>
21 Madbury Rd., Ste. 100, Durham, NH 03824<https://www.iol.unh.edu>
Mobile: +1-603-674-2755<https://www.iol.unh.edu>
lylavoie@iol.unh.edu<https://www.iol.unh.edu>
    <https://www.iol.unh.edu>

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.iol.unh.edu>
 <https://www.iol.unh.edu>
-- <https://www.iol.unh.edu>
Jill Lovato<https://www.iol.unh.edu>
Senior PR Manager <https://www.iol.unh.edu>
The Linux Foundation<https://www.iol.unh.edu>
jlovato@linuxfoundation.org <https://www.iol.unh.edu>
Skype: jill.lovato1<https://www.iol.unh.edu>
Phone: +1.503.703.8268<https://www.iol.unh.edu>

<https://www.iol.unh.edu>
 <https://www.iol.unh.edu>
-- <https://www.iol.unh.edu>
Mara Bernazzani<https://www.iol.unh.edu>
Communications Coordinator<https://www.iol.unh.edu>
UNH InterOperability Laboratory<https://www.iol.unh.edu>
21 Madbury Rd, Suite 100, Durham, NH 03824<https://www.iol.unh.edu>
mbernazzani@iol.unh.edu<https://www.iol.unh.edu>
1-603-862-0901 (o)<https://www.iol.unh.edu>
  <https://www.iol.unh.edu>

Interested to learn more? Sign up for our quarterly newsletter for industry news and IOL happenings.

<https://www.iol.unh.edu>
 <https://www.iol.unh.edu>
-- <https://www.iol.unh.edu>
Jill Lovato<https://www.iol.unh.edu>
Senior PR Manager <https://www.iol.unh.edu>
The Linux Foundation<https://www.iol.unh.edu>
jlovato@linuxfoundation.org <https://www.iol.unh.edu>
Skype: jill.lovato1<https://www.iol.unh.edu>
Phone: +1.503.703.8268<https://www.iol.unh.edu>

<https://www.iol.unh.edu>
 <https://www.iol.unh.edu>
-- <https://www.iol.unh.edu>
*******************************************************************************<https://www.iol.unh.edu>
Lincoln Lavoie<https://www.iol.unh.edu>
Senior Engineer, Broadband Technologies<https://www.iol.unh.edu>
 <https://www.iol.unh.edu>
[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png]<https://www.iol.unh.edu>
www.iol.unh.edu<https://www.iol.unh.edu>
21 Madbury Rd., Ste. 100, Durham, NH 03824<https://www.iol.unh.edu>
Mobile: +1-603-674-2755<https://www.iol.unh.edu>
lylavoie@iol.unh.edu<https://www.iol.unh.edu>
[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/facebook.png]  [http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/twitter.png]   [http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/linkedin.png] <https://www.iol.unh.edu>
 <https://www.iol.unh.edu>
Ars sine scientia nihil est! -- Art without science is nothing.<https://www.iol.unh.edu>
Scientia sine ars est vacua! -- Science without art is empty.<https://www.iol.unh.edu>
 <https://www.iol.unh.edu>
Broadband Forum Gfast Certified Product List<https://www.iol.unh.edu>
*******************************************************************************<https://www.iol.unh.edu>

<https://www.iol.unh.edu>
 <https://www.iol.unh.edu>
-- <https://www.iol.unh.edu>
Jill Lovato<https://www.iol.unh.edu>
Senior PR Manager <https://www.iol.unh.edu>
The Linux Foundation<https://www.iol.unh.edu>
jlovato@linuxfoundation.org <https://www.iol.unh.edu>
Skype: jill.lovato1<https://www.iol.unh.edu>
Phone: +1.503.703.8268<https://www.iol.unh.edu>

[-- Attachment #2: Type: text/html, Size: 38997 bytes --]

Re: [dpdk-ci] [dpdk-marketing] Results are now public

[Jeremy Plsek]

[-- Attachment #1: Type: text/plain, Size: 14514 bytes --]

Sure, I'll post it soon.

On Tue, Nov 20, 2018 at 8:58 AM O'Driscoll, Tim <tim.odriscoll@intel.com>
wrote:

> That’s great. I think there should be a post to the announce@dpdk.org
> list to draw attention to this.
>
>
>
> Jeremy: Do you want to send this, since you and the UNH team did a lot of
> the work to get it set up?
>
>
>
> *From:* Jill Lovato [mailto:jlovato@linuxfoundation.org]
> *Sent:* Monday, November 19, 2018 5:55 PM
> *To:* Lincoln Lavoie <lylavoie@iol.unh.edu>
> *Cc:* Mara Bernazzani <mbernazzani@iol.unh.edu>; Tu, Lijuan <
> lijuan.tu@intel.com>; O'Driscoll, Tim <tim.odriscoll@intel.com>; Thomas
> Monjalon <thomas@monjalon.net>; jplsek@iol.unh.edu; Yigit, Ferruh <
> ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org;
> pmacarth@iol.unh.edu
> *Subject:* Re: [dpdk-marketing] [dpdk-ci] Results are now public
>
>
>
> Awesome! Thank you!
>
>
>
> The blog is live:
> https://www.dpdk.org/blog/2018/11/19/dpdk-community-lab-publishes-relative-performance-testing-results/
>
>
>
> We'll update with the second image.
>
>
>
> On Mon, Nov 19, 2018 at 9:52 AM Lincoln Lavoie <lylavoie@iol.unh.edu>
> wrote:
>
> 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@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@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@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@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@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@dpdk.org] On Behalf Of O'Driscoll, Tim
> > Sent: Friday, November 16, 2018 6:14 AM
> > To: Thomas Monjalon <thomas@monjalon.net>; Jeremy Plsek
> > <jplsek@iol.unh.edu>
> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; ci@dpdk.org;
> > marketing@dpdk.org; Lincoln Lavoie <lylavoie@iol.unh.edu>; Patrick
> > MacArthur <pmacarth@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@dpdk.org to let
> > people know about it.
> >
> > > -----Original Message-----
> > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > Sent: Wednesday, November 14, 2018 10:17 PM
> > > To: Jeremy Plsek <jplsek@iol.unh.edu>
> > > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh
> > > <ferruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; Lincoln
> > > Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur
> > > <pmacarth@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@dpdk.org and dpdklab@iol.unh.edu.
> > > >
> > > >
> > > >
> > > > Thanks!
> > > >
> > > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@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@intel.com wrote:
> > > > >>
> > > > >>
> > > > >>
> > > > >> > -----Original Message-----
> > > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > > >> > Sent: Friday, November 9, 2018 2:02 PM
> > > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
> > > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy Plsek
> > > > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@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@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* <https://www.iol.unh.edu>
>
> 21 Madbury Rd., Ste. 100, Durham, NH 03824 <https://www.iol.unh.edu>
>
> Mobile: +1-603-674-2755 <https://www.iol.unh.edu>
>
> *lylavoie@iol.unh.edu* <https://www.iol.unh.edu>
>
>      <https://www.iol.unh.edu>
>
>
>
> 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.iol.unh.edu>
>
>   <https://www.iol.unh.edu>
>
> -- <https://www.iol.unh.edu>
>
> *Jill Lovato <https://www.iol.unh.edu>*
>
> Senior PR Manager <https://www.iol.unh.edu>
>
> The Linux Foundation <https://www.iol.unh.edu>
>
> *jlovato@linuxfoundation.org*  <https://www.iol.unh.edu>
>
> Skype: jill.lovato1 <https://www.iol.unh.edu>
>
> Phone: +1.503.703.8268 <https://www.iol.unh.edu>
>
>
> <https://www.iol.unh.edu>
>
>   <https://www.iol.unh.edu>
>
> -- <https://www.iol.unh.edu>
>
> Mara Bernazzani <https://www.iol.unh.edu>
>
> Communications Coordinator <https://www.iol.unh.edu>
>
> UNH InterOperability Laboratory <https://www.iol.unh.edu>
>
> 21 Madbury Rd, Suite 100, Durham, NH 03824 <https://www.iol.unh.edu>
>
> *mbernazzani@iol.unh.edu* <https://www.iol.unh.edu>
>
> 1-603-862-0901 (o) <https://www.iol.unh.edu>
>
>    <https://www.iol.unh.edu>
>
>
>
> Interested to learn more? *Sign up* for our quarterly newsletter for
> industry news and IOL happenings.
>
>
> <https://www.iol.unh.edu>
>
>   <https://www.iol.unh.edu>
>
> -- <https://www.iol.unh.edu>
>
> *Jill Lovato <https://www.iol.unh.edu>*
>
> Senior PR Manager <https://www.iol.unh.edu>
>
> The Linux Foundation <https://www.iol.unh.edu>
>
> *jlovato@linuxfoundation.org*  <https://www.iol.unh.edu>
>
> Skype: jill.lovato1 <https://www.iol.unh.edu>
>
> Phone: +1.503.703.8268 <https://www.iol.unh.edu>
>
>
> <https://www.iol.unh.edu>
>
>   <https://www.iol.unh.edu>
>
> -- <https://www.iol.unh.edu>
>
>
> *******************************************************************************
> <https://www.iol.unh.edu>
>
> *Lincoln Lavoie <https://www.iol.unh.edu>*
>
> Senior Engineer, Broadband Technologies <https://www.iol.unh.edu>
>
>   <https://www.iol.unh.edu>
>
> <https://www.iol.unh.edu>
>
> *www.iol.unh.edu* <https://www.iol.unh.edu>
>
> 21 Madbury Rd., Ste. 100, Durham, NH 03824 <https://www.iol.unh.edu>
>
> Mobile: +1-603-674-2755 <https://www.iol.unh.edu>
>
> *lylavoie@iol.unh.edu* <https://www.iol.unh.edu>
>
>      <https://www.iol.unh.edu>
>
>   <https://www.iol.unh.edu>
>
> Ars sine scientia nihil est! -- Art without science is nothing.
> <https://www.iol.unh.edu>
>
> Scientia sine ars est vacua! -- Science without art is empty.
> <https://www.iol.unh.edu>
>
>   <https://www.iol.unh.edu>
>
> *Broadband Forum Gfast Certified Product List* <https://www.iol.unh.edu>
>
>
> *******************************************************************************
> <https://www.iol.unh.edu>
>
>
> <https://www.iol.unh.edu>
>
>   <https://www.iol.unh.edu>
>
> -- <https://www.iol.unh.edu>
>
> *Jill Lovato <https://www.iol.unh.edu>*
>
> Senior PR Manager <https://www.iol.unh.edu>
>
> The Linux Foundation <https://www.iol.unh.edu>
>
> *jlovato@linuxfoundation.org*  <https://www.iol.unh.edu>
>
> Skype: jill.lovato1 <https://www.iol.unh.edu>
>
> Phone: +1.503.703.8268 <https://www.iol.unh.edu>
>
>

-- 
Jeremy Plsek
UNH InterOperability Laboratory

[-- Attachment #2: Type: text/html, Size: 38962 bytes --]