DPDK CI discussions
 help / color / Atom feed
From: Jill Lovato <jlovato@linuxfoundation.org>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: lijuan.tu@intel.com, "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
	 Thomas Monjalon <thomas@monjalon.net>,
	jplsek@iol.unh.edu, ferruh.yigit@intel.com,  ci@dpdk.org,
	marketing@dpdk.org, pmacarth@iol.unh.edu,
	 Mara Bernazzani <mbernazzani@iol.unh.edu>
Subject: Re: [dpdk-ci] [dpdk-marketing]  Results are now public
Date: Fri, 16 Nov 2018 08:42:06 -0800
Message-ID: <CANA499GDNRDhbfdDnV=khXD2JdjRo+gk+OJFT0nDdbKpzyXFXw@mail.gmail.com> (raw)
In-Reply-To: <CAOE1vsM6k=mT0Ds77YrJihtt=5zj1=MKKivnupzAqvMFU328bA@mail.gmail.com>

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

<div dir="ltr">Hi Lincoln,<div><br></div><div>Thanks for the update. We&#39;ll plan to post the blog Monday afternoon or Tuesday morning. </div><div><br></div><div>Have a great weekend,</div><div>Jill</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 15, 2018 at 6:49 PM Lincoln Lavoie &lt;<a href="mailto:lylavoie@iol.unh.edu">lylavoie@iol.unh.edu</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small">Hi All,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Mara our marketing lead is out for a vacation this week.  She&#39;s the keeper of all the good / approved pictures of the lab.  Should be able to get you something early next week.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Cheers,<br>Lincoln</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 15, 2018 at 9:29 PM Tu, Lijuan &lt;<a href="mailto:lijuan.tu@intel.com" target="_blank">lijuan.tu@intel.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Agree, I would like to see some photos of the lab.<br>
Should we add a brief introduction of contributors, this may attract more companies or individual to contribute to the lab.<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: ci [mailto:<a href="mailto:ci-bounces@dpdk.org" target="_blank">ci-bounces@dpdk.org</a>] On Behalf Of O&#39;Driscoll, Tim<br>
&gt; Sent: Friday, November 16, 2018 6:14 AM<br>
&gt; To: Thomas Monjalon &lt;<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</a>&gt;; Jeremy Plsek<br>
&gt; &lt;<a href="mailto:jplsek@iol.unh.edu" target="_blank">jplsek@iol.unh.edu</a>&gt;<br>
&gt; Cc: Yigit, Ferruh &lt;<a href="mailto:ferruh.yigit@intel.com" target="_blank">ferruh.yigit@intel.com</a>&gt;; <a href="mailto:ci@dpdk.org" target="_blank">ci@dpdk.org</a>;<br>
&gt; <a href="mailto:marketing@dpdk.org" target="_blank">marketing@dpdk.org</a>; Lincoln Lavoie &lt;<a href="mailto:lylavoie@iol.unh.edu" target="_blank">lylavoie@iol.unh.edu</a>&gt;; Patrick<br>
&gt; MacArthur &lt;<a href="mailto:pmacarth@iol.unh.edu" target="_blank">pmacarth@iol.unh.edu</a>&gt;<br>
&gt; Subject: Re: [dpdk-ci] [dpdk-marketing] Results are now public<br>
&gt; <br>
&gt; This looks good to me too. Some pictures would be nice, perhaps a snapshot<br>
&gt; of the dashboard some of the hardware in the lab. It would be good to get<br>
&gt; this posted on <a href="http://dpdk.org" rel="noreferrer" target="_blank">dpdk.org</a>, and send a note to <a href="mailto:announce@dpdk.org" target="_blank">announce@dpdk.org</a> to let<br>
&gt; people know about it.<br>
&gt; <br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: Thomas Monjalon [mailto:<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</a>]<br>
&gt; &gt; Sent: Wednesday, November 14, 2018 10:17 PM<br>
&gt; &gt; To: Jeremy Plsek &lt;<a href="mailto:jplsek@iol.unh.edu" target="_blank">jplsek@iol.unh.edu</a>&gt;<br>
&gt; &gt; Cc: O&#39;Driscoll, Tim &lt;<a href="mailto:tim.odriscoll@intel.com" target="_blank">tim.odriscoll@intel.com</a>&gt;; Yigit, Ferruh<br>
&gt; &gt; &lt;<a href="mailto:ferruh.yigit@intel.com" target="_blank">ferruh.yigit@intel.com</a>&gt;; <a href="mailto:ci@dpdk.org" target="_blank">ci@dpdk.org</a>; <a href="mailto:marketing@dpdk.org" target="_blank">marketing@dpdk.org</a>; Lincoln<br>
&gt; &gt; Lavoie &lt;<a href="mailto:lylavoie@iol.unh.edu" target="_blank">lylavoie@iol.unh.edu</a>&gt;; Patrick MacArthur<br>
&gt; &gt; &lt;<a href="mailto:pmacarth@iol.unh.edu" target="_blank">pmacarth@iol.unh.edu</a>&gt;<br>
&gt; &gt; Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public<br>
&gt; &gt;<br>
&gt; &gt; Looks great!<br>
&gt; &gt; I think adding pictures would be nice for the blog.<br>
&gt; &gt; Thank you<br>
&gt; &gt;<br>
&gt; &gt; 14/11/2018 22:07, Jeremy Plsek:<br>
&gt; &gt; &gt; With help from Lincoln and Patrick, below is an initial draft of the<br>
&gt; &gt; blog post.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; DPDK Community Lab Publishes Relative Performance Testing Results<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; The DPDK Community Lab is an open, independent testing resource for<br>
&gt; &gt; &gt; the DPDK project. Its purpose is to perform automated testing on<br>
&gt; &gt; &gt; incoming patch submissions, to ensure the performance and quality of<br>
&gt; &gt; &gt; DPDK is maintained. Participation in the lab is open to all DPDK<br>
&gt; &gt; &gt; project participants.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; For some time now, the DPDK Community Lab has been gathering<br>
&gt; &gt; &gt; performance deltas using the single-core packet I/O layer 2<br>
&gt; &gt; &gt; throughput test from DTS for each patch series submitted to DPDK<br>
&gt; &gt; &gt; compared to the master branch. We are pleased to announce that the<br>
&gt; &gt; &gt; Lab has recently been allowed to make these results public. These<br>
&gt; &gt; &gt; results are also now published to Patchwork as they are<br>
&gt; &gt; &gt; automatically generated. These results currently contain Mellanox<br>
&gt; &gt; &gt; and Intel devices, and the lab is able to support hardware from any<br>
&gt; &gt; &gt; DPDK participants wishing to support these testing efforts.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; To view these results, you can go to DPDK Community Lab Dashboard<br>
&gt; &gt; &gt; via the following link: <a href="https://lab.dpdk.org" rel="noreferrer" target="_blank">https://lab.dpdk.org</a>. The dashboard lists an<br>
&gt; &gt; &gt; overview of all active patch series and their results. Detailed<br>
&gt; &gt; &gt; results can be viewed by clicking on the patch series. If a patch<br>
&gt; &gt; &gt; fails to merge into master, a build log will show to help identify<br>
&gt; &gt; &gt; any issues. If a patch cleanly merges into master, performance delta<br>
&gt; &gt; &gt; results will show for each participating member.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; The Lab is hosted by the University of New Hampshire<br>
&gt; &gt; &gt; InterOperability Laboratory, as a neutral, third party location.<br>
&gt; &gt; &gt; This provides a secure environment for hosting equipment and<br>
&gt; &gt; &gt; generating unbiased results for all participating vendors. Lab<br>
&gt; &gt; &gt; participants, i.e. companies hosting equipment in the testing, can<br>
&gt; &gt; &gt; securely access their equipment through a VPN, allowing for<br>
&gt; &gt; &gt; maintenance and performance tuning, as the DPDK project progresses.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; The Lab works by polling the Patchwork API. When new patches are<br>
&gt; &gt; &gt; submitted, the CI server merges them with the master branch and<br>
&gt; &gt; &gt; generates a tarball. Each participating system unpacks and installs<br>
&gt; &gt; &gt; the DPDK tarball and then runs the performance testing against this<br>
&gt; &gt; &gt; DPDK build. When all systems have finished testing, the CI gathers<br>
&gt; &gt; &gt; the results into our internal database to be shown on the Dashboard,<br>
&gt; &gt; &gt; and sends final reports to Patchwork to show up on the submitted patch.<br>
&gt; &gt; &gt; This allows patch submitters to utilize Patchwork to view their<br>
&gt; &gt; &gt; individual results, while also allowing anyone to quickly see an<br>
&gt; &gt; &gt; overview of results on the Dashboard. The system provides<br>
&gt; &gt; &gt; maintainers with positive confirmation of the stability and<br>
&gt; &gt; &gt; performance of the overall project.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; In the future, we plan to open the Lab to more testing scenarios,<br>
&gt; &gt; &gt; such as performance testing of other features, beyond single-core<br>
&gt; &gt; &gt; packet I/O layer 2 throughput, and possibly running Unit Tests for DPDK.<br>
&gt; &gt; &gt; Additional features will be added to the Dashboard, such as showing<br>
&gt; &gt; &gt; graphs of the performance changes of master over time.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; If your company would like to be involved, email the Continuous<br>
&gt; &gt; &gt; Integration group at <a href="mailto:ci@dpdk.org" target="_blank">ci@dpdk.org</a> and <a href="mailto:dpdklab@iol.unh.edu" target="_blank">dpdklab@iol.unh.edu</a>.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Thanks!<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek &lt;<a href="mailto:jplsek@iol.unh.edu" target="_blank">jplsek@iol.unh.edu</a>&gt;<br>
&gt; &gt; wrote:<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; I can try to get it done later today, but I expect it to be more<br>
&gt; &gt; likely done on Monday.<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; On Fri, Nov 9, 2018, 9:08 AM O&#39;Driscoll, Tim<br>
&gt; &gt; &lt;<a href="mailto:tim.odriscoll@intel.com" target="_blank">tim.odriscoll@intel.com</a> wrote:<br>
&gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; -----Original Message-----<br>
&gt; &gt; &gt; &gt;&gt; &gt; From: Thomas Monjalon [mailto:<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</a>]<br>
&gt; &gt; &gt; &gt;&gt; &gt; Sent: Friday, November 9, 2018 2:02 PM<br>
&gt; &gt; &gt; &gt;&gt; &gt; To: O&#39;Driscoll, Tim &lt;<a href="mailto:tim.odriscoll@intel.com" target="_blank">tim.odriscoll@intel.com</a>&gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; Cc: Yigit, Ferruh &lt;<a href="mailto:ferruh.yigit@intel.com" target="_blank">ferruh.yigit@intel.com</a>&gt;; Jeremy Plsek<br>
&gt; &gt; &gt; &gt;&gt; &gt; &lt;<a href="mailto:jplsek@iol.unh.edu" target="_blank">jplsek@iol.unh.edu</a>&gt;; <a href="mailto:ci@dpdk.org" target="_blank">ci@dpdk.org</a>; <a href="mailto:marketing@dpdk.org" target="_blank">marketing@dpdk.org</a><br>
&gt; &gt; &gt; &gt;&gt; &gt; Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public<br>
&gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; 09/11/2018 14:58, O&#39;Driscoll, Tim:<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; From: Thomas Monjalon<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; 08/11/2018 14:01, Ferruh Yigit:<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; On 11/7/2018 7:30 AM, Thomas Monjalon wrote:<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; 06/11/2018 16:33, Jeremy Plsek:<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;&gt; Hi all,<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;&gt; This is just an update that all detailed results are<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;&gt; now<br>
&gt; &gt; &gt; &gt;&gt; &gt; public.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;&gt; If there is anything out of place, feel free to let me<br>
&gt; &gt; know!<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; It is really nice!<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; Thank you<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; Should we announce this in &#39;announce&#39; or &#39;dev&#39; mail lists?<br>
&gt; &gt; Many<br>
&gt; &gt; &gt; &gt;&gt; &gt; people<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; not aware<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; of this.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; It deserves an announce.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; And even a blog post I guess.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; +Cc marketing team<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; Agreed. I can do a quick post to <a href="mailto:announce@dpdk.org" target="_blank">announce@dpdk.org</a>. I believe<br>
&gt; &gt; Jeremy<br>
&gt; &gt; &gt; &gt;&gt; &gt; is working on a blog post which can provide more detail.<br>
&gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; Should we wait to have a blog post and reference it in the<br>
&gt; &gt; announce?<br>
&gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt;&gt; Good question. I think it depends how long the blog will take. If<br>
&gt; &gt; we can do it fairly quickly, then this is a good idea. If it&#39;s going<br>
&gt; &gt; to take a few weeks, then we should announce it now.<br>
&gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt;&gt; Jeremy: When do you think the blog will be ready?<br>
&gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; --<br>
&gt; &gt; &gt; Jeremy Plsek<br>
&gt; &gt; &gt; UNH InterOperability Laboratory<br>
&gt; &gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="m_-6458565752659430174gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><span style="font-size:12.8px">*******************************************************************************</span><br></div><div><b>Lincoln Lavoie</b><br></div><div>Senior Engineer, Broadband Technologies</div><div style="font-size:12.8px;word-wrap:break-word"><font color="#000000" face="Helvetica"><span style="font-size:12px"><br></span></font></div><div><a href="https://www.iol.unh.edu" target="_blank"><img src="http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png"></a><br></div><div><a href="https://www.iol.unh.edu" style="font-size:12.8px" target="_blank">www.iol.unh.edu</a><br></div><div>21 Madbury Rd., Ste. 100, Durham, NH 03824</div><div>Mobile: +1-603-674-2755<br></div><div><a href="mailto:lylavoie@iol.unh.edu" target="_blank">lylavoie@iol.unh.edu</a></div><div><a href="http://www.facebook.com/UNHIOL#" target="_blank"><img src="http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/facebook.png"></a>  <a href="https://twitter.com/#!/UNH_IOL" target="_blank"><img src="http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/twitter.png"></a>  <a href="http://www.linkedin.com/company/unh-interoperability-lab" target="_blank"><img src="http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/linkedin.png"></a><br></div><div><br></div><div>Ars sine scientia nihil est! -- Art without science is nothing.<br></div><div>Scientia sine ars est vacua! -- Science without art is empty.</div><div><br></div><div><a href="https://www.broadband-forum.org/implementation/interop-certification/gfast-certified-products" target="_blank">Broadband Forum Gfast Certified Product List</a></div><div><span style="font-size:12.8000001907349px">*******************************************************************************</span><br></div></div></div></div></div></div></div></div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><font color="#999999"><strong>Jill Lovato</strong></font></div><div><font color="#999999">Senior PR Manager </font></div><div><font color="#999999">The Linux Foundation</font></div><div><a href="mailto:jlovato@linuxfoundation.org" target="_blank">jlovato@linuxfoundation.org</a> </div><div><font color="#999999">Skype: jill.lovato1</font></div><div><font color="#999999">Phone: +1.503.703.8268</font></div></div></div></div></div></div></div>

  reply index

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 15:33 [dpdk-ci] " Jeremy Plsek
2018-11-07  7:30 ` Thomas Monjalon
2018-11-08 13:01   ` Ferruh Yigit
2018-11-08 13:10     ` Thomas Monjalon
2018-11-08 13:16       ` [dpdk-ci] [dpdk-marketing] " Trishan de Lanerolle
2018-11-08 13:37         ` Thomas Monjalon
2018-11-08 15:57         ` Jeremy Plsek
2018-11-09 13:58       ` O'Driscoll, Tim
2018-11-09 14:01         ` Thomas Monjalon
2018-11-09 14:07           ` Trishan de Lanerolle
2018-11-09 14:08           ` O'Driscoll, Tim
2018-11-09 15:03             ` Jeremy Plsek
2018-11-14 21:07               ` Jeremy Plsek
2018-11-14 22:16                 ` Thomas Monjalon
2018-11-15 22:13                   ` O'Driscoll, Tim
2018-11-15 22:30                     ` Jill Lovato
2018-11-16  2:29                     ` Tu, Lijuan
2018-11-16  2:48                       ` Lincoln Lavoie
2018-11-16 16:42                         ` Jill Lovato [this message]
2018-11-19 15:08                           ` Mara Bernazzani
2018-11-19 17:48                             ` Jill Lovato
2018-11-19 17:52                               ` Lincoln Lavoie
2018-11-19 17:55                                 ` Jill Lovato
2018-11-20  9:40                                   ` Thomas Monjalon
2018-11-20 13:58                                   ` O'Driscoll, Tim
2018-11-20 15:35                                     ` Jeremy Plsek

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANA499GDNRDhbfdDnV=khXD2JdjRo+gk+OJFT0nDdbKpzyXFXw@mail.gmail.com' \
    --to=jlovato@linuxfoundation.org \
    --cc=ci@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jplsek@iol.unh.edu \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=marketing@dpdk.org \
    --cc=mbernazzani@iol.unh.edu \
    --cc=pmacarth@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --cc=tim.odriscoll@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox