google/gVisor CI

[lubinsz]

Kind attention: @kalyxin02 @xiaobo55x Name, email, company, job title Bin Lu, bin.lu@arm.com, Arm, Staff software engineer

Project Title and description gVisor(https://github.com/google/gvisor) is a user-space kernel, written in Go, that implements a substantial portion of the Linux system surface.

Which members of the community would benefit from your work? Currently there are a bunch of contributions for this project, and together there is a need to have the fundamental integration test and unit test publicly now and furthermore the CI infrastructure in the future. This will encourage the contribution on multi-arch support, and thus appeal more gViosr developers to utilize this project. Also the google guys wants me to build an ARM CI for it.

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located? Yes.

https://github.com/google/gvisor

What infrastructure (computing resources and network access) do you need? (see: https://www.packet.net/bare-metal/)? Require access to ARM based Type 2A servers. Still in planning phase of how many, but starting off one should be sufficient.

As such - no long term support need is currently envisioned.

Please state your contributions to the open source community and any other relevant initiatives

I have enabled gvisor KVM platform to support Arm64. And also I delivered several patches to enable other modules, such as loader/arch/pagetable... Currently, the google guys want to run the kvm CI cases on Arm64 server.

Please let me know if you need more information. Thanks!!

[cayu53]

I assume that this is in response (and support of) https://github.com/google/gvisor/issues/1231

Happy to see one platform used to support this work. It would help if you could update this issue once things are in place and CI is running for Arm64 (and let the community know). If/when over time the upstream project has access to other Arm-based platforms for doing CI it would be good to update this ticket to provide visibility so we can review the needs etc.

Thanks,

[kalyxin02]

Hi Philippe,

Our team member Bin is currently working on that. Will update the ticket once we have progress.

Thanks Kaly

From: Philippe Robin notifications@github.com Sent: Wednesday, January 8, 2020 1:16 AM To: WorksOnArm/cluster cluster@noreply.github.com Cc: Kaly Xin Kaly.Xin@arm.com; Mention mention@noreply.github.com Subject: Re: [WorksOnArm/cluster] google/gVisor container CI (#189)

I assume that this is in response (and support of) google/gvisor#1231https://github.com/google/gvisor/issues/1231

Happy to see one platform used to support this work. It would help if you could update this issue once things are in place and CI is running for Arm64 (and let the community know). If/when over time the upstream project has access to other Arm-based platforms for doing CI it would be good to update this ticket to provide visibility so we can review the needs etc.

Thanks,

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/WorksOnArm/cluster/issues/189?email_source=notifications&email_token=AHVSU6IJZEHYJVGKQGAETYDQ4S2DJA5CNFSM4J3WZ3I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIJTCIY#issuecomment-571683107, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHVSU6ICQDCKMOHAFVK2FP3Q4S2DJANCNFSM4J3WZ3IQ.

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[lubinszARM]

cc @avagin @prattmic

[vielmetti]

Hi @lubinsz @lubinszARM - do you know which CI system you will be planning to use for this?

[lubinsz]

Hi @vielmetti It should be google kokoro ci system: https://github.com/googleapis/google-cloud-cpp/tree/master/ci/kokoro @avagin can you update more information? Thanks.

[vielmetti]

This has been approved - I'll follow up as soon as possible with access details.

[vielmetti]

@lubinsz - I have allocated one c2.large.arm (Ampere eMag) to a new project, and invited you to it. You can deploy the reserved hardware per these directions:

https://www.packet.com/developers/docs/getting-started/deployment-options/reserved-hardware/

It is quite possible that you'd also want to deploy on the c1.large.arm (Cavium ThunderX) and if you do decide to test or validate there just let me know.

Looking forward to getting any preliminary reports of success, I'll follow the upstream issue.

[lubinszARM]

@vielmetti Thank you very much.

[vielmetti]

Looks like positive progress, based on

https://github.com/google/gvisor/issues/1231

[vielmetti]

Reopening to reflect an access question (server wasn't showing up on available list).

[vielmetti]

@lubinsz The access question has been addressed, you should be able to provision the server now.

[lubinsz]

Hi @vielmetti The issue is gone. I can access the server now. Thanks.

[vielmetti]

The machine that's supporting this problem is having hardware issues, and it's been difficult to be in touch with the team running this by email. @lubinsz do you have an update?

[lubinszARM]

cc @zhlhahaha

[lubinszARM]

Hi @zhlhahaha Can you help to check this issue? Thanks.

[zhlhahaha]

Hi @zhlhahaha Can you help to check this issue? Thanks.

Hi @lubinszARM, thanks for informing me. I have replied @vielmetti via email.

[pgmwoa]

Closing the ticket as communicated the issue & resolved access of new project owners - Howard.Zhang@arm.com & Justin.He@arm.com