- kata-dev - lists.katacontainers.io

Handing over the community management reigns to Claire + Thierry
by Anne Bertucio 08 Oct '18

08 Oct '18

Hi all, If you didn't make the Architecture Committee call this morning, I will be handing over the Kata community management reigns to Thierry and Claire as I am moving on from my position at the Foundation. If you haven't met Thierry or Claire yet, you are in beyond capable hands. Thierry is the VP of Engineering at the OpenStack Foundation and is a wealth of knowledge about open source development. He is one of the drivers of the OpenStack Release Management team and I'd encourage you all to seek his advice as we continue to hammer out the Kata release process. Claire is the Senior Program Manager who oversees all new pilot projects (like Kata) at the Foundation. She's your go-to if you have questions about events, questions about other OSF projects, Kata marketing efforts, website edits, blog posts, etc. I will be around this week and next if you have any questions! Thierry Carrez, thierry(a)openstack.org, IRC/Slack: ttx Claire Massey, claire(a)openstack.org, Slack: @claire Cheers, Anne @whyhiannabelle | annabelleB Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

1 0

Gatekeepers!
by Whaley, Graham 08 Oct '18

08 Oct '18

Good morning, Welcome back those who had holiday weeks last week! This week's herders are: - Peng - James - Archana https://github.com/kata-containers/community/wiki/Review-Team-Rota#the-rota Yay, covered for all timezones! And, continuing thanks to all our volunteers. 40 PRs open (which is actually slightly less than I expected!) - and I noted last week whilst reviewing that we seem to have quite a lot of WIP/DNM PRs in flight. Graham --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

OpenStack Community Meeting - October 10 - Strategic Area Governance Update
by Chris Hoge 05 Oct '18

05 Oct '18

Following the interest in the first OpenStack Foundation community meeting, where we discussed the OpenStack Rocky release as well as quick updates from Kata, Airship, StarlingX and Zuul, we want to keep the community meetings going. The second community meeting will be October 10 at 8:00 PT / 15:00 UTC, and the agenda is for Jonathan Bryce and Thierry Carrez to share the latest plans for strategic project governance at the Foundation. These updates will include the process for creating new Strategic Focus Areas, and the lifecycle of new Foundation supported projects. We will have an opportunity to share feedback as well as a question and answer session at the end of the presentation. For a little context about the proposed plan for strategic project governance, you can read Jonathan’s email to the Foundation mailing list: http://lists.openstack.org/pipermail/foundation/2018-August/002617.html This meeting will be recorded and made publicly available. This is part of our plan to introduce bi-weekly OpenStack Foundation community meetings that will cover topics like Foundation strategic area updates, project demonstrations, and other community efforts. We expect the next meeting to take place October 24 and focus on the anticipated StarlingX release. Do you have something you'd like to discuss or share with the community? Please share them with me so that I can schedule them for future meetings. OpenStack Community Meeting - Strategic Area Governance Update Date & Time: October 10, 8:00 PT / 15:00 UTC Zoom Meeting Link: https://zoom.us/j/312447172 Agenda: https://etherpad.openstack.org/p/openstack-community-meeting Thanks! Chris Hoge Strategic Program Manager OpenStack Foundation

1 0

[Community] KubeCon NA attendance?
by Anne Bertucio 02 Oct '18

02 Oct '18

Hey all, One of the things we will talk about tomorrow in the Working Committee meeting (1500 UTC) is our plans for KubeCon North America in December, where Kata Containers will have a booth. We’ve tossed around ideas about office hours, live demos, etc., but it’d be helpful to get an idea of who is attending and who is interested in helping out with community activities like that. Who’s planning to be there? Cheers, Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

6 13

Embargo notice list for Kata now available
by Anne Bertucio 01 Oct '18

01 Oct '18

Hi all, We now have a mailing list set up for receiving embargoed notices of security vulnerabilities in Kata Containers. This list is intended for the appropriate security contact at downstream stakeholders (distros incorporating Kata, public clouds offering Kata to customers, etc) so they can coordinate releasing fixes before they are publicly disclosed. This list is for confidential announcements from the Kata vulnerability management team only; to report a vulnerability, please visit https://launchpad.net/katacontainers.io <https://launchpad.net/katacontainers.io> If you are a downstream consumer, you can send your security contact to subscribe here: http://lists.katacontainers.io/cgi-bin/mailman/listinfo/embargo-notice <http://lists.katacontainers.io/cgi-bin/mailman/listinfo/embargo-notice> Please let me know if you have any questions. Cheers, Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

1 0

Herding this week...
by Whaley, Graham 01 Oct '18

01 Oct '18

Good morning. Happy October! It looks like the herder this week is me :-) https://github.com/kata-containers/community/wiki/Review-Team-Rota I will note it is the Golden Week holidays in China this week - happy holidays if you are partaking! I've not yet figured out if that means we will clear down the PR list (as we may get fewer new PRs coming in), or if it might go up (as we have less review going on).... I guess we'll find out. Graham --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

2 2

Skip the arch committee of this week?
by Xu Wang 01 Oct '18

01 Oct '18

The following week will be public holidays in China, and I think most of the members from Hyper and Huawei will not be at work. Could we postpone the upcoming meeting to next time? -- Xu WangCTO & Cofounder, Hypergithub/twitter/wechat: @gnawuxhttp://hyper.sh Hyper_: Make VM run like container

2 2

Kata PR review rota
by Hunt, James O 28 Sep '18

28 Sep '18

We have a couple of free slots for next week if anyone would like to join Graham? - https://github.com/kata-containers/community/wiki/Review-Team-Rota (Don't worry - if you're in EMEA too, you can still help! :) A reminder - you *don't* need to be an expert in Kata / reviewing / golang / stuff: - http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000357.html Cheers, James --- https://katacontainers.io/ | https://github.com/kata-containers <https://github.com/clearcontainers> Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

OpenStack Summit Forum Submission Process Extended
by Jimmy McArthur 28 Sep '18

28 Sep '18

Hello Everyone We are extended the Forum Submission process through September 30, 11:59pm Pacific (6:59am GMT). We've already gotten a ton of great submissions, but we want to leave the door open through the weekend in case we have any stragglers. Please submit your topics here: https://www.openstack.org/summit/berlin-2018/call-for-presentations If you'd like to review the submissions to date, you can go to https://www.openstack.org/summit/berlin-2018/vote-for-speakers. There is no voting period, this is just so Forum attendees can review the submissions to date. Thank you! Jimmy

1 0

Namespaces in the host
by Montes, Julio 28 Sep '18

28 Sep '18

Hi All Currently Kata Containers only supports network namespaces in the host, other namespaces are not supported. This week I started to work on this but I faced some issues with the mount namespace in Go, the main issue is that a multithread process can't be reassociated with a new mount namespace [1] as it's reported here [2]. A solution for this might be to write a new binary in C to create and join namespaces and start the kata components (shim, qemu, etc) inside it, also this binary would be used to clean up (unmount, etc) the containers. Another solution might be to use a C constructor in Go (cgo) to create and join the namespace, but that means kata-runtime will run inside the namespace. If you are already working on this or know how to deal with this issue, please let me know. In the meantime I'll try to figure out how. Thank you! -- Julio [1] - http://man7.org/linux/man-pages/man2/setns.2.html [2] - https://github.com/golang/go/issues/8676

4 3

[ANNOUNCEMENT] Kata Containers 1.3.0 release and 1.2.2 stable release
by Tao Peng 28 Sep '18

28 Sep '18

Hello Kata Kats, I'm proud to announce that we have reached another milestone for Kata Containers by releasing the 1.3.0 release and 1.2.2 stable release. All users are recommended to upgrade. The 1.3.0 release highlights following features: - Network hotplug: Sandbox network can now be dynamically changed by the "kata-runtime network" subcommand. This allows customized CNI plugins to create more Kata-native network endpoints. - Network monitoring: a new kata component (kata-netmon) is added to monitor container netns on the host. Now CNI hooks to dynamically change the network setup of a running container, and "docker network connect" works with Kata Containers. - Network multiqueue support: Network cards are added to to the guest with multiqueue support. It allows Kata Containers to gain better network performance. - Memory hotplug: "kata-runtime update" subcommand can now add extra memory to a running container. - Better container memory constraint support: containers in the same sandbox can be constrained by memcg inside the guest. - GPU support: both GVT-g and GVT-d GPU devices can now be used by Kata Containers. - Architecture/arm64: add GICv4 or higher support. For full details, please see https://github.com/kata-containers/runtime/releases/tag/1.3.0 The 1.2.2 stable release also sees several important fixes and users who want to stick with stable-1.2 branch are recommended to update. For full details, please see https://github.com/kata-containers/runtime/releases/tag/1.2.2 Thanks to all contributors who have helped to make it happen! Cheers, Tao -- bergwolf(a)hyper.sh

4 3

About the future kata rootfs, qcow2 or nfs/vsock
by Qixuan Wu 28 Sep '18

28 Sep '18

Hi Stefan, Now we found 9pfs performance is poor, we are thinking of other solution for the rootfs of kata container. As per the link, https://github.com/kata-containers/runtime/issues/279. Seem you are doing about nfs/vsock optimization, and nfs/vsock seems that can possible be the future default rootfs of kata container. And I heard about qcow2+snapshot+virtio_scsi also. And how do you think about it as the rootfs of kata container? And do you know how the kata commumity think about this solution also and compare it with nfs/vsock ? Anything is welcome and helpful. Thanks & Regards Qixuan Wu.

7 24

/dev/urandom or /dev/random
by Boeuf, Sebastien 26 Sep '18

26 Sep '18

Hi folks, Following the discussion from this morning during the Arch committee meeting, I have investigated the sporadic issue https://github.com/kata-containers/runtime/issues/702 preventing from starting some Kata containers. I have been able to reproduce it pretty easily and I have identified it is related to the entropy of the host being almost entirely consumed by the first containers, leaving no time for the host to regenerate new entropy for the next containers. Currently, the virtio-rng device exposed by Qemu relies on /dev/random on the host, and because this device will block any access to it until some more entropy is ready, that's why we end up getting the timeout from the gRPC client as the agent is not ready, hence the gRPC server does not run yet (the guest is blocked on getting new entropy from /dev/random). One way to workaround this issue is to tweak the parameters of the virtio-rng device such as max-bytes=10, limiting the amount of entropy that can be consumed by the guest each period. This means that starting one container will not consume all host's entropy, but eventually, if we run a lot of containers, we'll be very likely to hit this same issue. The long term solution seems to rely on /dev/urandom device as this one will not block if no entropy is ready yet. But from what we can read online, it seems that some people have some security concerns about it. I'd like to understand if those worries are valid or not, and if we should keep thinking about another way to fix this issue. Thanks, Sebastien

13 17

Documentation for stable branch releases
by Hunt, James O 26 Sep '18

26 Sep '18

Hi all, We're having some discussion on how best to handle documentation for stable branch releases over on [1]. I don't want to repeat it all here, but the main question is whether we branch the doc repo [2] where we keep the installation guides and architecture doc. Currently, we only have a single doc repo branch so the existing install docs would need to handle all the releases we create going forward. Branching would be in line with our strategy for the other repos and would allow the release docs in each branch to only need to document how to install Kata for that particular release. There are of course costs associated with branching and there may be gotchas we haven't considered yet. Please feel free to join the conversation, particularly if you have experience with maintaining documentation for multiple release branches [3]. Cheers, James [1] - https://github.com/kata-containers/documentation/issues/234 [2] - https://github.com/kata-containers/documentation [3] - please, no pictures of your battle scars though! :) --- https://katacontainers.io/ | https://github.com/kata-containers <https://github.com/clearcontainers> Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.

1 0

I nominate user `marcov` to be a Kata Containers github maintainer
by Whaley, Graham 25 Sep '18

25 Sep '18

Hi all current maintainers. I know we discussed improving/defining the process we will use for officially adding maintainers to the Kata Containers github org recently. I forget the details we decided on (I know, they should be in the meeting minutes, and it is probably down for me to define and update the process on our documentation). However, for now we have a simple process defined at: https://github.com/kata-containers/community#maintainer Following that, I would like to nominate github user 'marcov' https://github.com/marcov to become a member of our org. I hereby present some supporting evidence: Marcov has been active in our Kat Herding review cycle: https://github.com/kata-containers/community/wiki/Review-Team-Rota Marcov has been active on contributing commits https://github.com/search?q=org%3Akata-containers+marcov&type=Commits As well as active in review and contribution to Issues and PRs: https://github.com/search?q=org%3Akata-containers+marcov&type=Issues Marcov is our SuSe package maintainer https://github.com/kata-containers/osbuilder/pull/161 And has been actively improving osbuilder. I will submit my +1 here :-) Graham --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

10 9

[Forum] Forum Topic Submission Period - Time Running out!
by Jimmy McArthur 24 Sep '18

24 Sep '18

Just a reminder that there is a little more than 60 hours left to submit your forum topics. Please make haste to the Forum submission tool: https://www.openstack.org/summit/berlin-2018/call-for-presentations Cheers, Jimmy > Jimmy McArthur <mailto:jimmy@openstack.org> > September 17, 2018 at 11:13 AM > Hello Everyone! > > The Forum Topic Submission session started September 12 and will run > through September 26th. Now is the time to wrangle the topics you > gathered during your Brainstorming Phase and start pushing forum > topics through. Don't rely only on a PTL to make the agenda... step on > up and place the items you consider important front and center. > > As you may have noticed on the Forum Wiki > (https://wiki.openstack.org/wiki/Forum) we're reusing the normal CFP > tool this year. We did our best to remove Summit specific language, > but if you notice something, just know that you are submitting to the > Forum. URL is here: > > https://www.openstack.org/summit/berlin-2018/call-for-presentations > > Looking forward to seeing everyone's submissions! > > If you have questions or concerns about the process, please don't > hesitate to reach out. > > Cheers, > Jimmy > > _______________________________________________ > Openstack-track-chairs mailing list > Openstack-track-chairs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs

1 0

Finalize Kata Mission Statement
by Anne Bertucio 24 Sep '18

24 Sep '18

Hi all, The Kata Mission Statement work has been going on in this issue[1], and if there’s no strong objections, I’d like to propose the following and close the issue: "Openly collaborate across a diverse, global community to define and implement secure, versatile containers solutions that combine the benefits of virtual machines with the performance and ease of containers” [1] https://github.com/kata-containers/community/issues/47 <https://github.com/kata-containers/community/issues/47> Cheers, Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

3 2

Herding this week
by Whaley, Graham 24 Sep '18

24 Sep '18

Good morning!, According to the rota page (https://github.com/kata-containers/community/wiki/Review-Team-Rota#the-rota) this week's herders are James and Ricardo. As ever, thanks to both of them, and let's all help them out where we can. Graham --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

Re: [kata-dev] CI automatic trigger is now disabled in the tests repository
by Fuentes, Salvador 21 Sep '18

21 Sep '18

Hello, So the automatic trigger is now disabled on all repos. You should be able to start the CI on the PRs using /test or /retest. Let me know if you find any issues. Regards. Salvador Fuentes Garcia QA Engineer. Open-source Technology Center > -----Original Message----- > From: Fuentes, Salvador [mailto:salvador.fuentes@intel.com] > Sent: Tuesday, September 18, 2018 6:40 PM > To: kata-dev(a)lists.katacontainers.io > Subject: [kata-dev] CI automatic trigger is now disabled in the tests repository > > Hello, > > Today I disabled the automatic build trigger from the CI but only on the tests > repository. This is mainly to make some tests before implementing this approach > across all repos. > So now every new PR opened on the tests repo will need to be verified by an > admin, who will be able to start the CI. > > The commands that can be used for triggering the builds are: > /test > /retest > retest this please - only for building failed jobs. > > We will need to run the commands on every change that is made on the PR. > > Limitations: > 1. The /retest command will rebuild all Jobs (including the ones that passed). It is > basically the same as /test. > The command that is use to only rebuild failed jobs cannot be changed from > the default one, which is: retest this please. > So we have 2 options to rebuild failed jobs: > 1. use the: "retest this please" command > 2. go to Jenkins directly and rebuild the job from there. > 2. The admin list can only be github users or organizations, so we won't be able > to use the kata-containers teams that are registered in github. This means that > all users registered in the kata-containers organization will be able to trigger the > CI on every repository. > > If someone wants to try this, there is a PR[1] where you can run the commands, > or you can use any other of the PRs in the tests repository. > If there are no comments or disagreements on this approach by tomorrow EOD, > I will enable the rest of the repositories to use this approach. > > Regards. > > [1] https://github.com/kata-containers/tests/pull/755 > Salvador Fuentes. > > > > > _______________________________________________ > kata-dev mailing list > kata-dev(a)lists.katacontainers.io > http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev

2 1

Contributor getting started guide
by Whaley, Graham 21 Sep '18

21 Sep '18

As discussed in Mondays call, Rico has written and added a (very nice) page to the wiki as a contributor quick start guide (one could almost say map) to how the project is structured: https://github.com/kata-containers/community/wiki/Getting-Started-Contribut… We discussed on Monday if this should live in the wiki, or be an MD doc in the docs or other repo. I'm happy for this to live in the wiki, and for us to then link off to it from the docs and/or contrib repo. Any objections? I've added a link to that and to some of the other wiki pages to our wiki homepage, as it was looking a bit un-loved... https://github.com/kata-containers/community/wiki Graham --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

Discuss Zuul on Sept 25 at 1900 UTC
by Anne Bertucio 21 Sep '18

21 Sep '18

Hi all, Sorry for the back and forth on coordinating a meeting to chat about the Zuul transition. The purpose of this discussion is to get everyone on the same page about where the Kata team is in transitioning to Zuul, what hasn’t been working currently, get some solutions from the OpenStack Infra team, etc. The easiest thing would be for the folks who are currently working on Jenkins/Zuul or interested in Kata’s CI to join the OpenStack Infra team’s weekly meeting next Tuesday, at 1900 UTC. They host their meetings on IRC freenode in #openstack-meeting [1]. Does that work for the people who would like to attend? [1] https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting <https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting> Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

3 3

Re: [kata-dev] [openstack-dev] Forum Topic Submission Period
by Jimmy McArthur 19 Sep '18

19 Sep '18

Sylvain Bauza wrote: > > > Le mer. 19 sept. 2018 à 00:41, Jimmy McArthur <jimmy(a)openstack.org > <mailto:jimmy@openstack.org>> a écrit : SNIP > > > Same as I do :-) Unrelated point, for the first time in all the > Summits I know, I wasn't able to know the track chairs for a specific > track. Ideally, I'd love to reach them in order to know what they > disliked in my proposal. They were listed on an Etherpad that was listed under Presentation Selection Process in the CFP navigation. That has since been overwritten w/ Forum Selection Process, so let me try to dig that up. We publish the Track Chairs every year. > SNIP > > I have another question, do you know why we can't propose a Forum > session with multiple speakers ? Is this a bug or an expected > behaviour ? In general, there is only one moderator for a Forum > session, but in the past, I clearly remember we had some sessions that > were having multiple moderators (for various reasons). Correct. Forum sessions aren't meant to have speakers like a normal presentation. They are all set up parliamentary style w/ one or more moderators. However, the moderator can manage the room any way they'd like. If you want to promote the people that will be in the room, this can be added to the abstract. > > -Sylvain > > > Cheers, > Jimmy > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

CI automatic trigger is now disabled in the tests repository
by Fuentes, Salvador 19 Sep '18

19 Sep '18

Hello, Today I disabled the automatic build trigger from the CI but only on the tests repository. This is mainly to make some tests before implementing this approach across all repos. So now every new PR opened on the tests repo will need to be verified by an admin, who will be able to start the CI. The commands that can be used for triggering the builds are: /test /retest retest this please - only for building failed jobs. We will need to run the commands on every change that is made on the PR. Limitations: 1. The /retest command will rebuild all Jobs (including the ones that passed). It is basically the same as /test. The command that is use to only rebuild failed jobs cannot be changed from the default one, which is: retest this please. So we have 2 options to rebuild failed jobs: 1. use the: "retest this please" command 2. go to Jenkins directly and rebuild the job from there. 2. The admin list can only be github users or organizations, so we won't be able to use the kata-containers teams that are registered in github. This means that all users registered in the kata-containers organization will be able to trigger the CI on every repository. If someone wants to try this, there is a PR[1] where you can run the commands, or you can use any other of the PRs in the tests repository. If there are no comments or disagreements on this approach by tomorrow EOD, I will enable the rest of the repositories to use this approach. Regards. [1] https://github.com/kata-containers/tests/pull/755 Salvador Fuentes.

4 5

OBS packaging reorganization proposal
by Marco Vedovati 19 Sep '18

19 Sep '18

Hi, we at SUSE think it would be great to have Kata Containers officially available in both openSUSE and SLE (enterprise) repositories. Our longer term vision is to integrate Kata Containers into the SUSE Container-as-a-Service platform as an additional container runtime. At the moment we support docker and cri-o, and kata looks like a nice addition :) This email is to propose a reorganization of the OBS packaging and get any feedback from you. I kicked off the discussion already with Carlos and Eric and this is the outcome: - Move all the packages on OBS from home:katacontainers to a new official development project under devel:kubic [1] (e.g. devel:kubic:katacontainers or whatever name you prefer). "devel" projects are associated with higher trust and visibility than "home" projects. - You can keep the build targets you currently have for the other distributions (Ubuntu, CentOS, etc...) - The relevant packages will be linked from devel:kubic:katacontainers to devel:kubic ("linking" is a way to avoid duplication of package sources), and from there we can set up the build targets to support all of the SUSE distribution flavours. This means that after a while [2], you can expect on any SUSE distribution to just do something like `sudo zypper install "kata-*"`, and have Kata Containers installed, without dealing with extra repositories. How does this sounds to you? Thanks, Marco [1]: https://kubic.opensuse.org/blog/2018-08-09-newdirection/ [2]: https://en.opensuse.org/openSUSE:Factory_development_model

2 1

Re: [kata-dev] CI automatic trigger is now disabled in the tests repository
by Fuentes, Salvador 19 Sep '18

19 Sep '18

> > One comment: > I wonder if the string "retest this please" can be replaced for " retest-this- > please" or "retest-failed" > Haven't found the way to change this string, but will continue investigating, hopefully there is a way. Salvador.

1 0