[kata-dev] Additional architecture support for Kata Containers: identifying owners for CI

Kevin Zhao Kevin.Zhao at arm.com
Thu May 31 02:28:57 UTC 2018

Hi Eric,

Thanks for help about Kata in Arm.

Adding Kaly from Arm. Kaly is leading container effort in Arm and she will get back answers after syncing with Arm internal stakeholders.
I think she will give you a good response.

Best Regards && Big Thx,
Kevin Zhao

From: Larrew, Jesse <Jesse.Larrew at amd.com>
Sent: Thursday, May 31, 2018 4:10 AM
To: Ernst, Eric <eric.ernst at intel.com>; Kevin Zhao <Kevin.Zhao at arm.com>; Hollingsworth, Brent <brent.hollingsworth at amd.com>; kata-dev at lists.katacontainers.io; Mohammed Naser <mnaser at vexxhost.com>; Clark Boylan <cboylan at sapwetik.org>
Subject: RE: Additional architecture support for Kata Containers: identifying owners for CI

Hi Eric,

I believe Brent has the action to get the CI infrastructure setup for AMD with SEV. There is a lab under construction at our new HQ in Santa Clara that should meet the requirements for CI, but we may be gated by the construction progress. Brent is the best contact (unless he recruits others to the cause). Thanks for following up on this!


From: Ernst, Eric [mailto:eric.ernst at intel.com]
Sent: Wednesday, May 30, 2018 2:39 PM
To: Kevin Zhao <Kevin.Zhao at arm.com<mailto:Kevin.Zhao at arm.com>>; Larrew, Jesse <Jesse.Larrew at amd.com<mailto:Jesse.Larrew at amd.com>>; Hollingsworth, Brent <brent.hollingsworth at amd.com<mailto:brent.hollingsworth at amd.com>>; kata-dev at lists.katacontainers.io<mailto:kata-dev at lists.katacontainers.io>; Mohammed Naser <mnaser at vexxhost.com<mailto:mnaser at vexxhost.com>>; Clark Boylan <cboylan at sapwetik.org<mailto:cboylan at sapwetik.org>>
Subject: Additional architecture support for Kata Containers: identifying owners for CI

Katazens –

There are several patches and discussions in place around support for additional hardware platforms in the Kata Containers project. This is great!  The three I’m aware of include AMD’s Epyc servers (leveraging SEV), 64B ARM (though I did talk to folks @ Open Stack Summit who were asking about 32b – can you clarify Kevin?) as well as ppc64le.

To facilitate this happening, we need CI in place for these architectures.  If it isn’t tested in our CI, we can’t effectively add support.

While we currently leverage Azure VMs for X86 testing, the CI tooling was created to be generic (we currently use Jenkins to drive the testing, though we are currently working with engineers on the Zuul project to see if this would be a better fit). Graham started an issue specific to ARM at [1].

For ARM:  I had discussions with Kevin Zhao while at Open Stack Summit, as well with Mohammed @ Vexxhost and Xu @ Hyper.sh. Each mentioned being able to help with appropriate support (whether it be dedicated machines sitting in an engineering department or baremetal machines offered via a cloud provider).  There were a lot of conversations, so mea culpa if I’m miss-remembering.   I want to coordinate and make sure we have a clear next step here on who can facilitate, and how/when.  Who will drive this for ARM?

For PPC and AMD with SEV: we would have similar requirements.  As Graham highlighted in [1], the current configuration using Jenkins can be seen at [2], though this would need adjustment to match the specific scenario (this is specific to our azure setup today).  Who’s the best point of contact for IBM?   Brent, same question for AMD SEV enabled machines (assuming support is to be added)?


[1] https://github.com/kata-containers/ci/issues/30
[2] https://github.com/kata-containers/ci/tree/master/jenkins
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.katacontainers.io/pipermail/kata-dev/attachments/20180531/37e53a33/attachment-0001.html>

More information about the kata-dev mailing list