Hi Kata-folk,
In addition to GitHub, Kata development relies on an external service,
PullApprove, in order to process PRs. This external service used to be
free-as-in-beer, but they recently decided[1] to change their terms of
service so that if "people who work on the repository get paid to do so,
then we need to get paid too". They are planning to flip the switch on
February 1, 2019.
Our read of their unclearly-specified conditions to apply for a free
plan concludes that we almost certainly would not qualify: despite the
project being open source and run by a non-profit Foundation, most of
the "people who work on the repository" get paid to do so.
We could of course comply with their reasonably-priced new terms (and
wait for the next bait-and-switch), but as an open source development
best practice it is generally better to reduce our dependency on such
external services, to avoid having the project be negatively affected by
the decisions of a third-party service provider.
Which is why I'm raising this thread, to tap the collective Kata mind
for solutions. In order of decreasing preference, we would find an
alternative solution that would
1- be open source, so that we could actually not depend on an additional
external service provider, or at least have the option to switch to
running it ourselves in case of sudden ToS changes
2- use built-in features of an external service we are already depending
on (GitHub)
3- use a free-as-in-beer external service provider that has already
published clear conditions for open source projects or projects run by
non-profit Foundations
Thoughts ?
[1] https://medium.com/dropseed/changes-to-our-free-plans-2660423c3f6
--
Thierry Carrez (ttx)
Good morning,
Herders this week are James and Rico.
https://github.com/kata-containers/community/wiki/Review-Team-Rota#the-rota
It feels like most folks are back from the vacation period now.
We have **62** open PRs I will note, that is trending UPWARDS. 17 of those are DNM.
I think we can attribute some of this rise to:
- the holiday season
- the project generally being more busy
- the difficulty and size of some of the PRs is increasing...
But, having said that, we do need to keep an eye on this and not allow the number of open PRs to escalate too far.
(to that end, I for one will see if I can visit some of my long standing PRs and nail them or close them...)
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.
Good morning - and *Happy New Year* :-)
I've updated the kat herder table over at:
https://github.com/kata-containers/community/wiki/Review-Team-Rota#the-rota
For the next 9 weeks or so (that seems to be our current rota cycle rate...).
The table contents are below - please.....
* check you are OK to do any weeks your name falls into
* add yourself into as many weeks as you like!
And remember - this is open to *anybody* - if you want to help out reviewing Kata pull requests, then just dive in. You don't have to be an expert or experienced - sometimes feedback is as simple as noting typos or CI failures or nudging folks on stale PRs that seem to be stuck, not moving, under-loved and maybe just forgotten.
| YYYY-MM-DD | APAC | EMEA | AMER | Notes
| ---------- | --------------------| ---------------------------- | ------------------------ |--------
| 2019-01-07 | | [jodh-intel] | [raravena80] | |
| 2019-01-14 | | [grahamwhaley] | | |
| 2019-01-21 | [bergwolf] | [jodh-intel] | [amshinde] | |
| 2019-01-28 | | [marcov] | [devimc] | |
| 2019-02-04 | [ydjainopensource] | | [raravena80] | |
| 2019-02-11 | | | [jcvenegas] | |
| 2019-02-18 | [caoruidong] | | [sboeuf] | |
Many thanks to all our herders - and may our 'flock' continue to thrive through 2019...
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.
Good morning Kat'ers,
As I'm sure you are all aware, we have just about entered the holiday season.
In theory, the official herders according to https://github.com/kata-containers/community/wiki/Review-Team-Rota#the-rota
Are...
Carlos, along with some Elves, Reindeer and maybe Santa himself if he gets his rounds done...
In reality, I suspect we will have no focused herders until maybe January the 2nd onwards... so... no matter where you are or what your plans are, I hope you all have a great break, and will see you back at the keyboard in the new year!
Graham (and the rest of the Herders...)
---------------------------------------------------------------------
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.
Happy winter-solstice-holiday-of-choice, kata-folk!
I am very pleased to announce 1.5.0-rc2 release of the Kata containers project. See the release page<https://github.com/kata-containers/runtime/releases/tag/1.5.0-rc2> for details.
This is an exciting release for Kata, which includes support for the Firecracker hypervisor, the s390x architecture as well as multiple fixes for shimv2 support.
Firecracker has been tested with CRIO+Kubernetes as well as Docker (18.06), with support for multiple network interfaces as well as (block based) volumes. A block-based storage driver, such as devicemapper, is required when using Kata with Firecracker. See this issue<https://github.com/kata-containers/runtime/issues/1071> for details on current volume limitations.
Firecracker is not currently packaged, but is available as part of our static-binary release tarball (available for download on the release page). I put together an initial wiki page with a quick start guide – take a look! Will work to get this into a proper repository after the holidays. https://github.com/kata-containers/documentation/wiki/Initial-release-of-Ka…<https://github.com/kata-containers/documentation/wiki/Initial-release-of-Ka…>
There aren’t any changes for 1.3 or 1.4 stable branches at this time, so no release was made for these.
Thanks for all the support on this release!
-Eric
Hi everyone,
Today, OSF distributed the second Open Infrastructure Community Newsletter. The bi-weekly newsletters provide a digest of the latest developments and activities across open infrastructure projects, events and users. This week, we highlighted Kata Containers turning one as well as a brief update about the upcoming Open Infrastructure Summit in Denver and additional OSF project news.
You can checkout the full newsletter on Superuser [1], and if you are interested in receiving the upcoming newsletters, you can subscribe here [2]. Kata Containers will have a small section included in each one.
If you would like to contribute to future newsletters or have feedback, please reach out to community(a)openstack.org <mailto:community@openstack.org>.
Thanks,
Claire
[1] http://superuser.openstack.org/articles/inside-open-infrastructure-12-19/ <http://superuser.openstack.org/articles/inside-open-infrastructure-12-19/>
[2] https://www.openstack.org/community/email-signup <https://www.openstack.org/community/email-signup>
Hi,
recently I've been working on updating kata packages with the goal to
have them integrated into the official openSUSE repositories and to
provide builds for more architectures.
This is a report of the current status. I'd like to have some feedback
from the community, and to know if you'd consider transitioning to this
new packaging structure.
Thanks,
Marco
Overview
We created a new development project on OBS, named
devel:kubic:katacontainers, that is supposed to host the most up-to-date
packages version, and will be used as source to submit packages update
to the official openSUSE repositories.
Me, Jose Carlos, Eric, and Peng Tao are maintainers for this project.
Here's the link:
https://build.opensuse.org/project/show/devel:kubic:katacontainers
Project content
- katacontainers: this contains all the host-side components, i.e. the
runtime, shim, proxy, ksm-throttler.
I decided to have a single package grouping all the go host-side
components, as all of them are needed to run kata containers on the
host, and as of now there are no use cases where a user may want to
cherry pick just some of them.
- katacontainers-kernel: kernel for the VM. This is the same package as
in home:katacontainers.
- qemu-lite: this is the same package as in home:katacontainers.
- kata-agent, kata-osbuilder, containment-rpm-kata: these are not meant
to be installed on the host. They are consumed by OBS and kiwi in order
to generate kata compatible VM images on OBS.
There's also a subproject named devel:kubic:katacontainers:images,
that's used to build kata VM images based on various distribution
flavours. As of now it contains:
- katacontainers-image-leap, katacontainers-image-tumbleweed: these are
rootfs images, built using kiwi and based on the openSUSE Leap and
Tumbleweed distributions. kiwi is able to build packages for other
distributions, both RPM and DEB based, so expect more to be added.
Supported Architectures
The current status is that packages work fine on x86_64 and aarch64. I
could not manage yet to find a suitable PPC machine to run tests. I also
enabled builds for s390x, and most of the packages can build
successfully on it.
Open points
- qemu-vanilla: I think that it should not be bundled with
katacontainers. Each distribution should rely on its own QEMU version.
- Clearlinux VM image: we could consider adding a pre-built x86_64 image.
- Debian / Ubuntu packages: I did not work on updated dsc/control files,
so it's something TODO. Contributors are welcome :)
- Nightlies, stable versions: TODO.
[Resend - the original may not have been delivered.]
Dear Kata Containers Community,
I'm delighted to announce the first release of virtio-fs, a new shared
file system for virtual machines that is designed for container use
cases, including shared volumes.
Unlike virtio-9p and NFS over AF_VSOCK, virtio-fs aims to take advantage
of the co-location between the virtual machine and the hypervisor in
order to achieve local file system semantics and improve performance.
For example, it can use Linux Direct Access (DAX) to access file
contents directly from the host page cache. This reduces communication
with the file server and avoids duplicating data into each sandbox VM.
It also means that mmap MAP_SHARED on a shared volume is coherent
between sandbox VMs.
The Linux kernel code (including performance numbers) has been posted
here:
https://marc.info/?l=linux-fsdevel&m=154446243324255&w=2
Kata Containers integration is already available so you can benchmark
and test virtio-fs. The project is under active development and we
still expect to make significant changes based on feedback and
collaboration.
We hope virtio-fs is interesting as a next step in overcoming
virtio-9p's performance and limitations. Let us know how it performs!
You can read more about virtio-fs here:
https://virtio-fs.gitlab.io/
The Kata HowTo is here:
https://virtio-fs.gitlab.io/howto-kata.html
The Kata runtime and agent changes are fairly straightforward and
comparable to virtio-9p. There are several other code changes due to
using a Fedora initramfs, systemd, and modular kernel. These are not
essential to virtio-fs but are simply how I preferred to develop and
test.
The FAQ on the virtio-fs website explains the main technical features.
Please let me know if you have any questions or need help getting it
running! I'm also on #kata-dev IRC if you need a hand.
Stefan
Good morning.
This week herders are:
- Yash
- Rico
https://github.com/kata-containers/community/wiki/Review-Team-Rota#the-rota
Yash, I know you are not too involved in the project at present - can you confirm if you will be able to dedicate us some time or not?
Everybody else, things looked like they got busy at the end of last week - thanks for your dedication, and I suspect we will all need to help try to keep on top of things this week.
** HEADS UP **
And then, as you are all no doubt aware, Christmas is rapidly approaching, which means for many of us a major vacation period.
I will predict that there will be few people online next Monday (24th), and unlikely to be back online until Wednesday January 2nd 2019 !
I also therefore don't think we will have any official herders next week (even if Carlos' name is in the table... ;-) ).
Let's see how much stuff we can squash this week....
For those heading for a vacation then, may you have an excellent time!
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.
Hi everyone,
As you know, Kata Containers is a pilot project supported by the OpenStack Foundation (OSF).
As such, we wanted to make sure you’re aware of an effort recently kicked off a sub group of the OSF Board of Directors to draft guidelines[1] for confirming pilot projects as full, top-level, open infrastructure project of the Foundation. The current pilot projects that will be eligible for confirmation review in 2019-2020 are Airship, Kata Containers, StarlingX and Zuul. Currently the OpenStack project is the only confirmed project.
The discussion about drafting these guidelines is just getting started, and *we invite you to participate in this effort* by reviewing the working draft in this etherpad and adding in your feedback and thoughts starting on line 139:
https://etherpad.openstack.org/p/BrainstormingOSFProjectConfirmationGuideli…
There will most likely be an open call scheduled in early 2019 where additional feedback will also be welcomed. I will share that invitation with you once it’s schedule.
The goal is to come up with a set of points that the Board can use when reviewing pilot projects for confirmation. This topic has previously been discussed at a very high-level at previous Board meetings, including the September 18th meeting[2] (starting around slide 38).
1. https://etherpad.openstack.org/p/ProjectConfirmationGuidelines
2. https://docs.google.com/presentation/d/10UyCpxkjPqC3kT-dYRpBxzNT39i2OhlggJv… <https://docs.google.com/presentation/d/10UyCpxkjPqC3kT-dYRpBxzNT39i2OhlggJv…>
Thanks,
Claire