Hi Tim, I don't disagree, I was assuming there might be a time where there are multiple labs as part of this or other testing programs within DPDK. I do like Thomas' proposal, "DPDK Community Lab," as it catches the main purpose of the lab, which to be a resource to the DPDK project participants. Cheers, Lincoln On Thu, Nov 8, 2018 at 8:24 AM O'Driscoll, Tim wrote: > We’ve mostly been referring to this as the “DPDK Open Lab”. It could also > be “DPDK Performance Lab”. I think the name needs to have DPDK in it. I > don’t think the name should include UNH-IOL. The lab is hosted by UNH-IOL, > but we need to emphasise the project rather than the location. > > > > Tim > > > > *From:* Lincoln Lavoie [mailto:lylavoie@iol.unh.edu] > *Sent:* Thursday, November 8, 2018 1:13 PM > *To:* thomas@monjalon.net > *Cc:* ci@dpdk.org; alialnu@mellanox.com; Tu, Lijuan ; > O'Driscoll, Tim ; web@dpdk.org > *Subject:* Re: [dpdk-ci] [PATCH] add a link to the CI dashboard > > > > Hi All, > > > > Would "UNH-IOL Performance Lab" be acceptable? I'm thinking this would be > along the lines of Host / Purpose. So, taking an example, if Acme hosted a > build lab, it could be "Acme Build Lab" or something like that. In terms > of project branding, maybe we need to develop some messaging around how the > labs are part of the project. I'm thinking similar to how OPNFV has the > "Pharos Labs," which they describe as "a federated NFV testing > infrastructure of community labs around the world." I think the goal would > be to describe the labs as a community resource, supporting to DPDK project > and it's developers. > > > > Cheers, > Lincoln > > > > On Thu, Nov 8, 2018 at 3:14 AM Thomas Monjalon > wrote: > > Note: such patch must be sent to web@dpdk.org. > > 08/11/2018 08:46, Ali Alnubani: > > --- a/content/perf-lab/_index.md > > +++ b/content/perf-lab/_index.md > > @@ -3,6 +3,10 @@ title = "Performance Lab" > > weight = "8" > > +++ > > > > +
> > + {{< button href="https://lab.dpdk.org" >}} CI Dashboard {{< /button > >}} > > +
> > It is important to keep in mind that we support a distributed CI approach. > This lab is an important part of the CI, but we can run other tests > in other labs. That's why I think we must really stick with a specific name > for this lab. > Several names were mentionned so far: > - performance lab > - UNH lab > - reference lab > - community lab > > I think we must decide which name we want to use. > Opinions? > > > > > -- > > > ******************************************************************************* > > *Lincoln Lavoie* > > Senior Engineer, Broadband Technologies > > > > > > www.iol.unh.edu > > 21 Madbury Rd., Ste. 100, Durham, NH 03824 > > Mobile: +1-603-674-2755 > > lylavoie@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 > > > > ******************************************************************************* > -- ******************************************************************************* *Lincoln Lavoie* Senior Engineer, Broadband Technologies www.iol.unh.edu 21 Madbury Rd., Ste. 100, Durham, NH 03824 Mobile: +1-603-674-2755 lylavoie@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 *******************************************************************************