September 2018 - kata-dev - lists.katacontainers.io

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 20 Sep '18

20 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 18 Sep '18

18 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

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

18 Sep '18

Hey Matt, Matt Riedemann wrote: > > Just a process question. Good question. > I submitted a presentation for the normal marketing blitz part of the > summit which wasn't accepted (I'm still dealing with this emotionally, > btw...) If there's anything I can do... > but when I look at the CFP link for Forum topics, my thing shows up > there as "Received" so does that mean my non-Forum-at-all submission > is now automatically a candidate for the Forum because that would not > be my intended audience (only suits and big wigs please). Forum Submissions would be considered separate and non-Forum submissions will not be considered for the Forum. The submission process is based on the track you submit to and, in the case of the Forum, we separate this track out from the rest of the submission process. If you think there is still something funky, send me a note via speakersupport(a)openstack.org or jimmy(a)openstack.org and I'll work through it with you. Cheers, Jimmy

1 0