[lustre-devel] Lustre Arm stuff status and work plan

Kevin Zhao kevin.zhao at linaro.org
Fri Feb 18 00:05:30 PST 2022

Hi All,

Greetings and thanks a lot for your comments! Xinliang and I are from Linaro
<https://www.linaro.org/>, 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? 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 <green at whamcloud.com> wrote:

> On Dec 27, 2021, at 8:53 PM, Xinliang Liu <xinliang.liu at 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
>> 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

*Best Regards*

*Kevin Zhao*

Tech Lead, LDCG Cloud Infrastructure

Linaro Vertical Technologies

IRC(freenode): kevinz

Slack(kubernetes.slack.com): kevinz

kevin.zhao at linaro.org | Mobile/Direct/Wechat:  +86 18818270915
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20220218/59f01fe4/attachment.html>

More information about the lustre-devel mailing list