From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from pdx1-mailman02.dreamhost.com (pdx1-mailman02.dreamhost.com [64.90.62.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 83229C433F5 for ; Fri, 18 Feb 2022 08:05:44 +0000 (UTC) Received: from pdx1-mailman02.dreamhost.com (localhost [IPv6:::1]) by pdx1-mailman02.dreamhost.com (Postfix) with ESMTP id EE12421CAF7; Fri, 18 Feb 2022 00:05:43 -0800 (PST) Received: from mail-oo1-f54.google.com (mail-oo1-f54.google.com [209.85.161.54]) by pdx1-mailman02.dreamhost.com (Postfix) with ESMTP id 9772121CA3F for ; Fri, 18 Feb 2022 00:05:42 -0800 (PST) Received: by mail-oo1-f54.google.com with SMTP id i10-20020a4aab0a000000b002fccf890d5fso2642524oon.5 for ; Fri, 18 Feb 2022 00:05:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IrzNotffqN0hBecqn/WKMqvepcJ9Nc9xSQ8wRdox22s=; b=BUmfaLXJmH/QY/AsGkQqOHHoLOXn0Nuis7JAOo0RwvyvmpDhg284gLSvrI9prsEJlZ 4GuCi/LW4INQaUdDAr+Z6nFEpSAXTH1vhZjj9efR58V9c0VcJu79Y4VJpJELE/gx9mdA YRa2qnPI3QAubElCJRlBY12nV5biVwMK9GXw3yHyENw4G5XARAag9wBdMATfd0Fqc1Fp 9T+D97RR4JKAEjFS8L9wNYreMiuOgWqsS6sfRUd9fZO5/rqBsAmN/C0oI3J4et+R/CWf NMh5PxQzUS91oTESLTCNl3RptDzms/vKwRlW2YmgJ0fzBtOPS0XjMHqddD4ArxY4Ckyh mIlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IrzNotffqN0hBecqn/WKMqvepcJ9Nc9xSQ8wRdox22s=; b=LZIcMR8RlvjDDQDjvau02H31R9mh184CXRYEmxHTSir6qXGofxK+iMftyIeu2ZQ408 jOzygM9vqjLxjChAJPJlpYgXSUNd2N8oBUCiKwqRvLaUNfXWg8Oc8N0fOLMLM71/YxmW Ntqg44Zw2vdsCjykMLAk0O3T2eQcrtlbeMz2HYjQIW0ouX66hZ8D3Sk/mFQ1vBAnrxFx ob1bcdBoB2xmTwc7Bg4StFKj6WYVRZoGyiDf8NJd3tSsm5Rou3fYByI/h+Il2eSs2CRE FTeVResjoB7c5gXYFEhAzmqwnl5FSQ5upEfNelx2Z85dlFmY7Q2aozgP8NaiwqUMq5oo 8mhA== X-Gm-Message-State: AOAM530U+pbtcGT3Y6Zk78zv/wvYEVJEoR2d+SANPCmV1dwaqcZR/HKl R8v2dBhiCvgOgHnjagXKXMyECbSuUUIPZFEA7ir1 X-Google-Smtp-Source: ABdhPJx7g+D+P8FuomLs0IcarAW1EznvQwmFjhWV/TRoFtNebedKCxfQtUfUDMpTv9vCFeEqEphxtHB7u1JIdPhHKV8= X-Received: by 2002:a05:6870:14cc:b0:ce:c0c9:649 with SMTP id l12-20020a05687014cc00b000cec0c90649mr4041327oab.155.1645171541552; Fri, 18 Feb 2022 00:05:41 -0800 (PST) MIME-Version: 1.0 References: <6C592E3F-0437-4776-BB29-C5EE489C5FAE@whamcloud.com> <7AAC4FDA-AC84-4E73-83AB-130B6BD3AE1B@whamcloud.com> <023CD146-E2BA-4B03-9459-C480E51EBE7E@whamcloud.com> In-Reply-To: <023CD146-E2BA-4B03-9459-C480E51EBE7E@whamcloud.com> Date: Fri, 18 Feb 2022 16:05:30 +0800 Message-ID: To: Oleg Drokin , mdiep@whamcloud.com Subject: Re: [lustre-devel] Lustre Arm stuff status and work plan X-BeenThere: lustre-devel@lists.lustre.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "For discussing Lustre software development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Kevin Zhao via lustre-devel Reply-To: Kevin Zhao Cc: Li Xi , Jian Yu , "cloud-dev-request@op-lists.linaro.org" , Xinliang Liu via lustre-devel Content-Type: multipart/mixed; boundary="===============4003944723233794852==" Errors-To: lustre-devel-bounces@lists.lustre.org Sender: "lustre-devel" --===============4003944723233794852== Content-Type: multipart/alternative; boundary="00000000000054465005d84659d1" --00000000000054465005d84659d1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi All, Greetings and thanks a lot for your comments! Xinliang and I are from Linar= o , an organization focusing on Arm open-source ecosystem development. We have been working on Lustre on the Arm64 server and client end for a while now, already fixing a few bugs on arm64. As Xinliang said before, we want to enable the Arm64 CI, Oleg advises that we can plug our own CI nodes into the Jenkins. Now we want to understand and estimate how many machines resources can meet our requests, and doing the next stage plan of our hardware to meet the Lustre test requirements. As I understand, the test jobs will cover the ZFS and Ldiskfs backend with 2 scenarios: - Lustre Arm64 Server + Arm64 Client( High Priority ) - Lustre Arm64 Server + x86_64 Client After going through the Lustre test website: https://testing.whamcloud.com/test_sessions, it is quite clear to show the test info, and still remain some questions, that will be great if the community can give me a clear answer. 1. Is there a link to show all the machine resources=EF=BC=9F Including the= machine info, CPU, memory and peripheral info. 2. Do we have a CI infra arch overview diagram to show the machine usage and communication? 3. How many machines are needed to meet the request of the Lustre Arm64 Server + Arm64 Client test? Thanks a lot for your time, and look forward to your response. On Tue, 28 Dec 2021 at 09:58, Oleg Drokin wrote: > > > On Dec 27, 2021, at 8:53 PM, Xinliang Liu wrote= : > > Maloo is just one place to link to to actually let people see the results= , >> but you can link to external resources too >> like e.g. gatekeeper janitor helper does or assuming the information is >> small enough it could be entirely contained >> in the comment (like say for a build failure) >> > > Ok, understand now. Is there any other reference external CI that posts > results to Lustre gerrit now? > > > Currently there are: > - checkpatch and Misc code checks (smach) that post their results as 100% > comment only. they share codebase pretty much > - the Janitor (also started with above codebase but got changed and > extended a lot) > > There was external interest in the past to post results to gerrit but it > never materialized in the end > --=20 *Best Regards* *Kevin Zhao* Tech Lead, LDCG Cloud Infrastructure Linaro Vertical Technologies IRC(freenode): kevinz Slack(kubernetes.slack.com): kevinz kevin.zhao@linaro.org | Mobile/Direct/Wechat: +86 18818270915 --00000000000054465005d84659d1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi All,

=

Greetings and thanks a lot for your comm= ents! Xinliang and I are from Linaro, an organization focusing on Arm open-source ecosystem development= . We have been working on Lustre on the Arm6= 4 server and client end for a while now, already fixing a few bugs on arm64= .

As Xinliang said before, we want to enable the Arm64 CI, Oleg advises that we can plug our own= CI nodes into=C2=A0the Jenkins. Now = we want to understand and estimate how many machines resources can meet our= requests, and doing the next stage plan of our hardware to meet the Lustre= test requirements.


As I understand, the test jobs will cover the ZFS and Ldiskfs= backend with 2 scenarios:

After going throug= h the Lustre test website: https://testing.whamcloud.com/test_s= essions, it is quite clear to sh= ow the test info, and still remain some questions, that will be great if th= e community can give me a clear answer.

1. Is there a link to show all the machine resources=EF=BC=9F Inclu= ding the machine info, CPU, memory and peripheral info.=C2=A0

2. Do we have a CI infra arch overview diagra= m to show the machine usage and communication?=C2=A0

3. How many machines are needed to meet the request of= the Lustre Arm64 Server + Arm64 Client test?


Thanks a lot for your tim= e, and look forward to your response.



On Tue, 28 Dec 2021 at 09:58, Oleg Drokin <green@whamcloud.com> wrote:
<= /div>


On Dec 27, 2021, at 8:53 PM, Xinliang Liu <xinliang.liu@linaro.org> wrote:=

Maloo is just one place to link to to actually let people see the results, = but you can link to external resources too
like e.g. gatekeeper janitor helper does or assuming the information is sma= ll enough it could be entirely contained
in the comment (like say for a build failure)

Ok, understand now. Is there any other reference external CI that post= s results to Lustre gerrit now?

Currently there are:
- checkpatch and Misc code checks (smach) that post their results as 1= 00% comment only. they share codebase pretty much
- the Janitor (also started with above codebase but got changed and ex= tended a lot)

There was external interest in the past to post results to gerrit but = it never materialized in the end


--
Best Regards

Kevin Zhao

Tech Lead, LDCG Cloud Infrastructure=

<= font color=3D"#757b80">Linaro Vertical = Technologies

IRC(= freenode): kevinz

Slack(kubernetes.slack.com): kevinz

kevin.zhao@linaro.org=C2=A0| Mobile/Direct/Wechat:=C2=A0 +86 = 18818270915=C2=A0


--00000000000054465005d84659d1-- --===============4003944723233794852== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lustre-devel mailing list lustre-devel@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org --===============4003944723233794852==--