From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com
[66.111.4.29]) by dpdk.org (Postfix) with ESMTP id D3AD6493D;
Thu, 8 Nov 2018 14:28:27 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by mailout.nyi.internal (Postfix) with ESMTP id 6CDFB201E3;
Thu, 8 Nov 2018 08:28:27 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163])
by compute1.internal (MEProxy); Thu, 08 Nov 2018 08:28:27 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
from:to:cc:subject:date:message-id:in-reply-to:references
:mime-version:content-transfer-encoding:content-type; s=mesmtp;
bh=O9uHNuez3ewzADe+vENCOI+KnZU5dw1czNgQEaK+25k=; b=QkyHLdaIz8yr
ulDDhBtKfIS+v9gWnih/eN0I5zBE3b9zpZmPNBrulbQxLzOApAVZB9tLJA8RWnQn
0OZrNjn+Y+8ADXlVD/YO0jYQ5gAQ4S4kjnCNGeVjOVPOoYx8VEBo8zWg9hW4Epbv
BquqWJR/a/MXHYN/MIJRVHlvECTqxCA=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=cc:content-transfer-encoding:content-type
:date:from:in-reply-to:message-id:mime-version:references
:subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
:x-sasl-enc; s=fm1; bh=O9uHNuez3ewzADe+vENCOI+KnZU5dw1czNgQEaK+2
5k=; b=TDqdZ1eJn6HYyibUkcFjcqov3+F87pgkm/jzrzpO2HrmzvIyvt+G9yKoA
6WL+uMPmYzdWfbFEk4T9IrJ18RMbQjr5nvHABlF6YIdp5PclHGb+zil8xd8GqoIx
/4d2STgYgzhMzmvZUymJ1mf/1hkNbXKybFpasVzOGGlNsNO3GNC+/JBk86bIcyt2
CvUCYmAAuLAqEs+g+DblFQyJYPT9YbV9GzSDrjlglfoe/ha4FJ/3cahKyV3fsgJj
47ofl2aU0nbnngdC4OQhRg0syEdn0efBtNEicJwqCB/X5q9shFdwBxIkBcgQiH+8
yd2rNZ+GaWC5LOjLdb9rL6KDVb4+Q==
X-ME-Sender: <xms:-jnkW88GzXs8_uK6CcytXS6RWtm_KvvqS8ehbcRsNC6UsohcNA77zA>
X-ME-Proxy: <xmx:-jnkWzLvzoX3yakuDlEB_xsjTrIKmchHp5SGkGhBq0RKHMqyY1sTDg>
<xmx:-jnkW9zdtQ0g7SNPd78L4VdyN-sZG4I5_ENsY9TfxfGrfgeJ8doXug>
<xmx:-jnkWy0M0f4B-IMez_H6RedJHVTHV6S0M89LAtBKjbU2afckC5vE3w>
<xmx:-jnkW5V0FdukoprSkiA9iiZDyHKm-W2jORBP6B2o7x9kfgVzzRNnnw>
<xmx:-jnkW-AlMoZe1KNItu6O0DdTQSRmDvPGY2GmxEPDeK0tgRWOHB9pZw>
<xmx:-znkW8jobLZ3_8CSY0FuB1RZDqg2yOIIP4PzahLL0dy7f6sTonbquA>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
by mail.messagingengine.com (Postfix) with ESMTPA id C27D3103F9;
Thu, 8 Nov 2018 08:28:25 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: ci@dpdk.org, alialnu@mellanox.com, lijuan.tu@intel.com,
tim.odriscoll@intel.com, web@dpdk.org
Date: Thu, 08 Nov 2018 14:28:24 +0100
Message-ID: <32826685.tUcjU3XkpW@xps>
In-Reply-To: <CAOE1vsPucqZBSxMN4N_FE=p_3Ccam2ppczNtF018JOEtcSUfVQ@mail.gmail.com>
References: <20181108074622.5215-1-alialnu@mellanox.com>
<3354634.DNSllWXiY1@xps>
<CAOE1vsPucqZBSxMN4N_FE=p_3Ccam2ppczNtF018JOEtcSUfVQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-ci] [PATCH] add a link to the CI dashboard
X-BeenThere: ci@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK CI discussions <ci.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/ci>,
<mailto:ci-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/ci/>
List-Post: <mailto:ci@dpdk.org>
List-Help: <mailto:ci-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/ci>,
<mailto:ci-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2018 13:28:28 -0000
08/11/2018 14:13, Lincoln Lavoie:
> On Thu, Nov 8, 2018 at 3:14 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> > 08/11/2018 08:46, Ali Alnubani:
> > > + {{< 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?
>
> 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.
I agree we must improve the communication about the distributed CI.
Starting with good naming is a good step for communicating :)
Let's discuss your proposal "UNH-IOL Performance Lab".
About "UNH-IOL", yes it is accurate, but we may want to show it as
THE lab which is shared by several community members, not only
the lab hosted at UNH.
About "Performance" word, I think we should avoid that name
because the lab will probably be used for functionnal testing as well.
Another proposal sent in parallel of this mail by Tim: "DPDK Open Lab".
I am in favor of "DPDK Community Lab".