- kata-dev - lists.katacontainers.io

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

19 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

Architecture Committee election results
by Anne Bertucio 19 Sep '18

19 Sep '18

Hi all, First off, thank you to our outgoing Architecture Committee members for their work, time, and care for the Kata community! Thank you for leading us through our first 6 months of shaping this new open source project and for helping guiding us to a 1.0 release. Secondly, congratulations to the newly elected Architecture Committee members [1]: -Eric Ernst -Wei Zhang -Jon Olson They will join Xu Wang and Samuel Ortiz on the Architecture Committee. Thank you to everyone who participated in the first Kata Containers elections! Cheers, Anne [1] https://github.com/kata-containers/community/pull/61/files <https://github.com/kata-containers/community/pull/61/files> Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

8 8

Forum Topic Submission Period
by Jimmy McArthur 17 Sep '18

17 Sep '18

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

1 0

Kat Herders schedule updated (**PLEASE CHECK**)
by Whaley, Graham 17 Sep '18

17 Sep '18

Hi all, Our Kat Herders schedule table was running out - I've refreshed it by taking all the old entries in the table and moving them to the end - effectively I've wrapped the table around. Thus **NOTE** - if you have been a Kat Herder before then you are probably now entered into a new slot sometime in the near future... Please check if that is acceptable and/or correct or you are available - and either edit the Wiki page or let me know if you cannot herd for that week. https://github.com/kata-containers/community/wiki/Review-Team-Rota I'll try to paste a copy of the table as well - apologies for the HTML email, and any non-translation etc. YYYY-MM-DD APAC EMEA AMER Notes 2018-09-17 grahamwhaley<https://github.com/grahamwhaley> egernst<https://github.com/egernst> 2018-09-24 jodh-intel<https://github.com/jodh-intel> raravena80<https://github.com/raravena80> 2018-10-01 grahamwhaley<https://github.com/grahamwhaley> 2018-10-08 bergwolf<https://github.com/bergwolf> amshinde<https://github.com/amshinde> 2018-10-15 devimc<https://github.com/devimc> 2018-10-22 ydjainopensource<https://github.com/ydjainopensource> jodh-intel<https://github.com/jodh-intel> raravena80<https://github.com/raravena80> 2018-10-29 caoruidong<https://github.com/caoruidong> marcov<https://github.com/marcov> jodh-intel<https://github.com/jodh-intel> jcvenegas<https://github.com/jcvenegas> 2018-11-05 sboeuf<https://github.com/sboeuf> Thanks! 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

Kat Herders this week
by Whaley, Graham 17 Sep '18

17 Sep '18

This weeks nominated Kat Herder is EricE. I've also added myself in to the EMEA timezone slot, and will try to make some time to push on some PRs. https://github.com/kata-containers/community/wiki/Review-Team-Rota 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

Zuul job disabled on runtime repo
by Fuentes, Salvador 14 Sep '18

14 Sep '18

Hi, Recently we have faced some issues with the Zuul jobs and most of them are now failing. I have disabled the Zuul job on the runtime repo to prevent noise when reviewing PRs. I'll work next week with the Openstack team to see how can we fix the current issues and after fixing them, I'll re-enable the jobs. Regards. Salvador Fuentes Garcia QA Engineer. Open-source Technology Center

2 2

metrics CI tracking proxy/agent/shim PRs
by Whaley, Graham 12 Sep '18

12 Sep '18

Hi all, Thanks to the generosity of Packet.net and the CNCF, we have gained some hardware resource to enable metrics CI tracking. I've configured and hooked up an instance to track PRs on the proxy/agent/shim repos. You may/will start to notice an extra 'jenkins-metrics-ubuntu-16-04' item appear in the CI checks list for those repos. This should be *non-blocking* whilst we settle the system - but, be aware, even non-blocking CI failure items stop the big merge button going green - it will be grey, and still allow you to merge, if a non-blocking item fails. As you may now need to check metrics CI failures, the 'quick' route is to go to the Jenkins console log output of the relevant build (via the link off the github status), and scroll to near the bottom of the console. You should find (given the CI built and ran OK), a summary table that looks something like this: Report Summary: +-----+----------------------+-------+--------+--------+-------+--------+--------+-------+------+-----+ | P/F | NAME | FLR | MEAN | CEIL | GAP | MIN | MAX | RNG | COV | ITS | +-----+----------------------+-------+--------+--------+-------+--------+--------+-------+------+-----+ | P | boot-times | 95.0% | 98.4% | 105.0% | 10.0% | 94.1% | 103.7% | 10.2% | 2.3% | 20 | | P | memory-footprint | 95.0% | 100.4% | 105.0% | 10.0% | 100.4% | 100.4% | 0.0% | 0.0% | 1 | | P | memory-footprint-ksm | 95.0% | 97.0% | 105.0% | 10.0% | 97.0% | 97.0% | 0.0% | 0.0% | 1 | +-----+----------------------+-------+--------+--------+-------+--------+--------+-------+------+-----+ Fails: 0, Passes 3 Check the P/F column - anything with a '*F*' will be a failure case, and cause the CI to fail. And, yes, improving the documentation about how to set up, configure, and read the results is on 'the list' :-) You are basically looking for the MEAN to fall between the FLR(floor) and CEIL(celing) of expected results. Once we are happy the checks are stable we will enable them across the other repos (runtime, tests etc.), and make them blocking. 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 1

Kat Herders this week
by Whaley, Graham 10 Sep '18

10 Sep '18

Good morning!, Kat Herders for this week (https://github.com/kata-containers/community/wiki/Review-Team-Rota#the-rota) ... Sebastien. This is one of the weeks when we only have one reviewer listed on the wiki ... if you feel you can step up and help a bit with reviewing and nudging PRs this week, please: - feel free to shout - edit the wiki page to reflect your intentions - or just plain get stuck in! ;-) I know I've been somewhat absent from PR review for a couple of weeks - and if I get my little backlog cleared down in the next couple of days will try to find some time to go have a reviewing session... 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 1

6 days left for the Forum Brainstorming Period...
by Jimmy McArthur 06 Sep '18

06 Sep '18

Hello All! The Forum Brainstorming session ends September 11 and the topic submission phase begins September 12. Thank you to all of the projects that have created a wiki and begun the Brainstorming Phase. I'd like to encourage projects that have not yet created an etherpad to do so at https://wiki.openstack.org/wiki/Forum/Berlin2018 This is an opportunity to get feedback, vet ideas, and garner support from the community on your ideas. Don't rely only on a PTL to make the agenda... step on up and place the items you consider important front and center :) If you have questions or concerns about the process, please don't hesitate to reach out. Cheers, Jimmy

1 0

Re: [kata-dev] Kata Forum @ Berlin Summit - REMINDER to submit ideas for public discussion
by LaBrecque, Margaret 06 Sep '18

06 Sep '18

I’m going to send weekly reminders … and maybe more often as we approach the deadline of 9/21 :) (After 9/21, I’ll compile the inputs for review on the 9/24 Arch Committee so we can hit the official 9/26 deadline for the mid-November Berlin Openstack Summit.) From: LaBrecque, Margaret Sent: Wednesday, August 29, 2018 3:11 PM To: Anne Bertucio <anne(a)openstack.org>; kata-dev(a)lists.katacontainers.io Subject: RE: [kata-dev] Kata Forum @ Berlin Summit Hi – Folks can now add suggestions for the Kata Forum topic at the November Berlin Summit (described by Anne below). To seed the discussion, I made up some examples in the Etherpad – please submit your ideas! https://etherpad.openstack.org/p/KataBerlinForum There are 3 sample Forum discussions suggested: * Strategic – longer term view of the project – e.g., How is container security evolving and how will Kata evolve to stay relevant? * Cross-project – collaborating with the broader community of related projects * Project-specific – e.g., What features are important to make Kata easier to deploy in production? Open sharing of any such experiences. * …? We have until Sept 26 to gather, triage and submit Forum discussion ideas. Margaret Intel Open Source Technology Center From: Anne Bertucio <anne(a)openstack.org<mailto:anne@openstack.org>> Sent: Tuesday, August 28, 2018 5:06 PM To: kata-dev(a)lists.katacontainers.io<mailto:kata-dev@lists.katacontainers.io> Subject: [kata-dev] Kata Forum @ Berlin Summit Hi all, At the Vancouver Summit in May, we used some of our in-person work time to hear from potential Kata users on what they would like to see in the project, what blockers to use were, use cases they wanted to support (like particular kernel versions, etc). At the Berlin Summit, we have the opportunity to have these talks in a more “official” way by taking part in the “Forum” track. The Forum track is a set of 40 minute discussion sessions (vs presentations) on particular topics that have been selected by a Selection Committee (made up of representatives from the OpenStack Technical Committee, OpenStack User Committee, StarlingX, Airship, Zuul, and Kata Containers[!!—see the next section for details on this bit]). The idea of the Forum track is to hear user and potential user feedback, and take that into consideration for future development cycles. There is a period (now through September 12) of open brainstorming done via etherpad [1], as a community we decide what we want to submit by September 26, and then final sessions are selected by the Committee. Even if you will not be in Berlin, you can still add topics to the etherpad. We are also looking for one Kata Containers volunteer to serve on this selection committee. Don’t be intimidated if you don’t know the ins and outs of the other projects in the Forum track. The main job is the make sure all sessions are discussion-based proposals that recognize the user-developer open source feedback loop (not sales pitches, etc). It’s ~6-9 hours of work in total, a few calls. You get to become more familiar with other open source projects and community members, and be a part of the design/develop/deploy open source cycle. Let me know if you’re interested in volunteering on the selection committee or if you have questions about the process. Hope many of you will be able to make it to Berlin! [2] [1] https://etherpad.openstack.org/p/KataBerlinForum [2] https://www.openstack.org/summit/berlin-2018/ Anne Bertucio OpenStack Foundation anne(a)openstack.org<mailto:anne@openstack.org> | irc: annabelleB

1 0

[AC][Election] Questions
by Ricardo Aravena 03 Sep '18

03 Sep '18

Questions, (some of them came up in my talk at the OSS) 1) I believe this came up before, but what are the plans to tie docker or kubernetes container resource definitions/utilization to the specific resources running in QEMU. For example, if in kubernetes we specify that our container needs 2Gib of RAM how are we going to tie it into the Kata configuration. Is that going to work seamlessly with hotplug? Are there any plans to work with the Kubernetes/Docker communities to make this work seamlessly? 2) Looks like the focus in the upcoming year is to make Kata more stable, scalable, adopted, etc. Part of getting more adoption is to support other Hypervisors, so how soon (priority wise) do you see support for other hypervisors like Hyper-V, and Xen? Which one would be next to support? 3) It looks like there are vulnerabilities that also affect VMs, such as the L1 Terminal Fault (L1TF). In terms of addressing are there any plans for mitigating these besides what the Hypervisors or VM runtimes (KVM, Xen, etc) might provide? 4) Are there any plans to add support to make easy for cluster operators/server admins to debug the VM? I mean we can always attach to the serial port but would be nice to have some tools to make it easy to debug. Thanks!

2 2

Kata Architecture Committee voting is now open
by Anne Bertucio 03 Sep '18

03 Sep '18

Hi all, If you are eligible to vote in the Kata Architecture Committee election, you should have just received an email from civs(at)cs.cornell.edu <http://cs.cornell.edu/> with a unique link to vote. Please check your spam/junk if you do not see the email, and contact me if you think you should have received a ballot but did not. The poll uses condorcet voting. It is essentially ranking, but with a bit more nuance than just a 1-4 rank: Give each of the following choices a rank, where a smaller-numbered rank means that you prefer that choice more. For example, give your top choice the rank 1. Give choices the same rank if you have no preference between them. You do not have to use all the possible ranks. All choices initially have the lowest possible rank. If you haven’t used condorcet voting before, you can read about it here [1]. We will announce the results the week of September 11. If you have any questions about the process or issues voting, please let me know. Otherwise, good luck to all of our fantastic candidates! Cheers, Anne [1] https://civs.cs.cornell.edu/rp.html <https://civs.cs.cornell.edu/rp.html> Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

1 0

答复: [AC][Election] Is this project progressing at a healthy rate?
by zhangwei (CR) 03 Sep '18

03 Sep '18

Hi All, > Is this project currently progressing at a “healthy” rate? (Ie sustainable for contributors, while not losing momentum and interest from potential users). If so, how do we keep it going? If it isn’t, how do you propose we get on track? I will give a positive answer, so far we’re doing quite well ☺ To keep this going, I think there’re several things we can do in following days: 1. Keep it cool! The first time I know Hyper runV and Intel Clear Containers, I thought it’s a really cool idea, I believe everyone else has same feelings, a good first impression drove me to learn more about these project. So keeping Kata Containers cool can attract new developers. To keep it cool, we can continuously add new features from qemu/kernel/K8S to kata containers and make sure our developers always has something new to play :-p 2. Stability again! To persuade developers stay in community, Kata Containers need to prove to developers/users that it’s a mature and successful project, stability is best sign of maturity which gives users confidence to Kata Containers because no one wants to put lots of effort to a failing project. 3. Make it widely used! Which means more platform support, more hardware support, more hypervisor support etc, then anyone on any platform can run it in production. Just my 2 cents. Thank you! -Wei 发件人: Anne Bertucio [mailto:anne@openstack.org] 发送时间: 2018年9月1日 1:54 收件人: kata-dev(a)lists.katacontainers.io 主题: [kata-dev] [AC][Election] Is this project progressing at a healthy rate? Another question for our Architecture Committee Candidates! Most folks mentioned something about stability, plugins, integrations that needed to happen to be a production ready project. My second question for you all is: Is this project currently progressing at a “healthy” rate? (Ie sustainable for contributors, while not losing momentum and interest from potential users). If so, how do we keep it going? If it isn’t, how do you propose we get on track? Anne Bertucio OpenStack Foundation anne(a)openstack.org<mailto:anne@openstack.org> | irc: annabelleB

1 0

This weeks herders...
by Whaley, Graham 03 Sep '18

03 Sep '18

Good morning, This week's Kat Herders are: - Marco (welcome!) - JamesH - Carlos https://github.com/kata-containers/community/wiki/Review-Team-Rota As ever, not being on the list does not mean you cannot, or should not, review ;-) This is Marco's first week Herding and really being hands on in Kata - so, please welcome him to the herd, and help where you can. Thanks! 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

Canceling 9/3 Arch Meeting
by Anne Bertucio 03 Sep '18

03 Sep '18

Hi all, Apologies for the late notice, but tomorrow is a major US holiday so we probably wouldn’t have any of our US friends (or US-based employers) on the call, so we’ll skip the Arch meeting and cover things off via email. Cheers, Anne

3 2

[release] update on stable branches
by Ernst, Eric 01 Sep '18

01 Sep '18

With help from Carlos and Salvador, the necessary changes are in place for our CI and release tooling to be able to support management of both stable branches and master. As you may already be aware, the branches stable-1.1 and stable-1.2 have been created and populated. On Friday we made a release on this, as well as packages on OBS. You can find details on this at [1] and [2]. I haven’t announced this widely yet, as I’m first looking for closure on: 1. Merge of stable branch documentation, see [3] and [4]. [4] is mostly a copy/reformat of the google doc that I received feedback on. The PR could still use some additional clarity – please chime in. 2. Updated guidelines for users on how to install Kata (stable and master packages are now available). See [5]. This was a pretty tedious process, and I appreciate the efforts in getting our infrastructure ready to support stable releases. Please take a look at the open issues regarding documentation and provide guidance. Thanks, Eric [1] - https://github.com/kata-containers/runtime/releases/tag/1.2.1 [2] - https://github.com/kata-containers/runtime/releases/tag/1.1.1 [3] – https://github.com/kata-containers/documentation/issues/237 [4] - https://github.com/kata-containers/documentation/pull/238 [5] - https://github.com/kata-containers/documentation/issues/234

2 1

[AC] Arch Committee Election: Q&A period open!
by Anne Bertucio 01 Sep '18

01 Sep '18

Hi all, We have four candidates for the Architecture Committee election—names and links to their ML posts below. The next week is for asking questions to candidates via this mailing list; it’s an opportunity to get familiar with the perspective they would bring as an Arch Committee member before voting opens the week of the 3rd. To kick off Q&A week: What is the most important thing (be it an integration, a particular feature, adopting a policy, etc) Kata Containers needs to achieve in the next year and how should we get there? Candidates (in alphabetical order): -Eric Ernst [1] -Jon Olson [2] -Kaly Xin [3] -Wei Zhang [4] [1] http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000337.html <http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000337.html> [2] http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000341.html <http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000341.html> [3] http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000333.html <http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000333.html> [4] http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000330.html <http://lists.katacontainers.io/pipermail/kata-dev/2018-August/000330.html> Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

5 4

[AC][Election] Is this project progressing at a healthy rate?
by Anne Bertucio 31 Aug '18

31 Aug '18

Another question for our Architecture Committee Candidates! Most folks mentioned something about stability, plugins, integrations that needed to happen to be a production ready project. My second question for you all is: Is this project currently progressing at a “healthy” rate? (Ie sustainable for contributors, while not losing momentum and interest from potential users). If so, how do we keep it going? If it isn’t, how do you propose we get on track? Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

1 0

Volunteers for Kat herding next week?
by Hunt, James O 31 Aug '18

31 Aug '18

Hi All, # TL;DR If you'd like to get more exposure to Kata, please consider adding your name to the PR reviewer rota here: - https://github.com/kata-containers/community/wiki/Review-Team-Rota (If you don't have permission to do this, please let us know [1]). As shown, there are a few gaps which are just waiting for you to put your name in! :) # Myth busting - You don't need to be a repo maintainer - You don't have to have done it before :) - You *can* do it again :) - There is no limit on the number of folk on the rota for a particular week If someone already has their name down, you can add yours too! [2]. Ideally, we'd have lots of folk on the rota every week in all the different regions. - You don't need to have read the PR review guide (although it should help) It's just a guide and offers some thoughts on things to look out for. - You don't have to spend the entire week doing it We appreciate any time you can offer to help clear the PR backlogs. And finally to the biggest myth of them all... - You most certainly do *NOT* need to be an expert in golang or Kata All contributions are appreciated. Further, we encourage everyone to ask as many "silly questions" on PRs as possible. Such "silly questions" are invaluable in helping "shake out" what on earth the author was thinking at the time they wrote the code (or doc) and can provide extremely valuable feedback to them as they may have made incorrect assumptions. What we're striving for is of course correct code (and doc) but also code/doc that looks almost embarrassingly simple. If it looks too complex and/or the design/intent is not clear, the PR needs to be improved imho. We do this by gently guiding the author to a simpler, clearer result by asking questions and making suggestions (politely :) # Reasons to help out - Kudos of course! - You'll be helping the project increase velocity (getting all those new features and bug fixes landed faster!) - Learn more about how Kata works. - Learn about our processes. - Find areas that interest you. There are still a lot of "low-hanging fruit" issues if you're looking for an area to start contributing to: https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+org%3Akata-… https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+org%3Akata-… https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+org%3Akata-… - Learn how to debug Kata. - Learn how our CI works and how to debug issues. - ... and did I mention all the Kudos you'll get? :) - Kudos # Further info - https://github.com/kata-containers/community/blob/master/CODE_OF_CONDUCT.md (This one you do have to read and agree to :) - https://github.com/kata-containers/community/blob/master/PR-Review-Guide.md - https://github.com/kata-containers/community/blob/master/Documentation-Revi… - https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md Cheers, James [1] - https://github.com/kata-containers/community#join-us [2] - To add multiple names to a github table cell, use "<br/>" like this: | users1 <br/> user2 <br/> user3 | --- 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.

2 2

Kata Forum @ Berlin Summit
by Anne Bertucio 30 Aug '18

30 Aug '18

Hi all, At the Vancouver Summit in May, we used some of our in-person work time to hear from potential Kata users on what they would like to see in the project, what blockers to use were, use cases they wanted to support (like particular kernel versions, etc). At the Berlin Summit, we have the opportunity to have these talks in a more “official” way by taking part in the “Forum” track. The Forum track is a set of 40 minute discussion sessions (vs presentations) on particular topics that have been selected by a Selection Committee (made up of representatives from the OpenStack Technical Committee, OpenStack User Committee, StarlingX, Airship, Zuul, and Kata Containers[!!—see the next section for details on this bit]). The idea of the Forum track is to hear user and potential user feedback, and take that into consideration for future development cycles. There is a period (now through September 12) of open brainstorming done via etherpad [1], as a community we decide what we want to submit by September 26, and then final sessions are selected by the Committee. Even if you will not be in Berlin, you can still add topics to the etherpad. We are also looking for one Kata Containers volunteer to serve on this selection committee. Don’t be intimidated if you don’t know the ins and outs of the other projects in the Forum track. The main job is the make sure all sessions are discussion-based proposals that recognize the user-developer open source feedback loop (not sales pitches, etc). It’s ~6-9 hours of work in total, a few calls. You get to become more familiar with other open source projects and community members, and be a part of the design/develop/deploy open source cycle. Let me know if you’re interested in volunteering on the selection committee or if you have questions about the process. Hope many of you will be able to make it to Berlin! [2] [1] https://etherpad.openstack.org/p/KataBerlinForum <https://etherpad.openstack.org/p/KataBerlinForum> [2] https://www.openstack.org/summit/berlin-2018/ <https://www.openstack.org/summit/berlin-2018/> Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

2 1

Deadline AUGUST 30 - Berlin Summit Travel Support
by Claire Massey 30 Aug '18

30 Aug '18

Hi everyone, OSF covers travel costs (hotel and/or flight) for a limited quantity of applicants for each Summit. The deadline to apply for Travel Support to the November Berlin Summit closes TOMORROW, Thursday, August 30 at 11:59pm PT. If your company will not cover costs for you to attend the Berlin Summit <https://www.openstack.org/summit/berlin-2018/>, then you’re welcome to APPLY HERE <https://openstackfoundation.formstack.com/forms/travelsupportberlin>. The Travel Support Program's aim is to facilitate participation of active community members to the Summit by covering the costs for their travel and accommodation. If you are a key contributor to a project managed by the OpenStack Foundation, and your company does not cover the costs of your travel and accommodation to Berlin, you can apply for the Travel Support Program. Please email summit(a)openstack.org <mailto:summit@openstack.org> with any questions. Thanks, Claire

1 0

Users and their areas of interest
by Hunt, James O 29 Aug '18

29 Aug '18

I've put together a rough table showing some of the users and their areas of interest / specialist areas: https://github.com/kata-containers/community/wiki/Areas-of-interest This page could be useful for those raising PRs as they can look over the table and then add a few folk as explicit reviewers. It could also be useful for the weeks Kool Kats [1] to, again, manually add explicit reviewers for those PRs without much activity If I've offended you by either missing you out mis-specifying your interests, I humbly apologise [2]. It's a first cut so there are bound to be mistakes - feel free to update it [3] :) Cheers, James. [1] - https://github.com/kata-containers/community/wiki/Review-Team-Rota [2] - If the spelling of that word offends you, I humbly apologize. [3] - But if you don't have privs, please let us know and we'll fix it: https://github.com/kata-containers/community#join-us --- 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.

2 4

Kat herders for the week
by Whaley, Graham 28 Aug '18

28 Aug '18

Good morning, (apologies for posting on Tuesday - yesterday was a public holiday here...) Kat Herders for this week are Yash, James and Ricardo. https://github.com/kata-containers/community/wiki/Review-Team-Rota I'm aware that both Yash and Ricardo may not have merge rights on the repos, so maintainers, please be vigilant and try and move those merges along (Yash, Ricardo, feel free to drag the maintainers in when necessary!) Thanks! 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

Reminder: Berlin Summit tickets increase Aug 28
by Anne Bertucio 27 Aug '18

27 Aug '18

Hi all, Quick reminder that early bird tickets for the OpenStack Summit Berlin, November 13-15, end in ~30 hours: August 28 at 11:59pm PT/August 29 at 6:59 UTC. The early bird price is $699 USD for a full access pass; goes up to $999 USD after early bird. There’s a handful of awesome looking Kata sessions [1], there’s talks from heaps of other open source projects and plenty of opportunities to meet these folks and chat about the integration points with Kata, as well as meet with other Kata Kats! It’s also a great opportunity for us to talk with potential Kata users and get input on technical direction. You can snag that early bird price on Eventbrite [2]. Hope to see you there! [1] https://www.openstack.org/summit/berlin-2018/summit-schedule/global-search?… <https://www.openstack.org/summit/berlin-2018/summit-schedule/global-search?…> [2] https://www.eventbrite.com/e/openstack-summit-november-2018-berlin-tickets-… <https://www.eventbrite.com/e/openstack-summit-november-2018-berlin-tickets-…> Anne Bertucio OpenStack Foundation anne(a)openstack.org | irc: annabelleB

1 0

Kata Arch Council Candidacy Declaration - Jon Olson
by Jon Olson 27 Aug '18

27 Aug '18

Name: Jon Olson Email: jonolson(a)google.com Background: I am a staff software engineer at Google working on the core virtualization and I/O layer backing Google Compute Engine. My work is focused on resource footprint minimization as well as performance optimization and stability. Part of this work is improving our support for containerized workloads and ensuring it is aligned with the needs of our customer community (e.g., Kata users). My involvement with the Kata community has included being a regular attendee at the weekly Kata Arch Council meetings. To these meetings I’ve brought context from my work building and maintaining a hypervisor that supports long-lived workloads at scale, as well as the occasional PR for getting Kata running in GCE. I believe whole workload containment via virtualization is a key component to addressing the broad problem of container security. Having a strong, open solution to that problem is critical to ensuring all workloads can run securely, regardless of where they are deployed. I enjoy working with the Kata community to build such a solution, and look forward to many more core-hours of security contained workloads. Jon

2 1