pdostal

How-to guide on switching from docker/docker-compose to a cri-o/k8s world In this project I basically want to explore how you can move your containers (including its data and overlayfs2 layers) from Docker based docker-compose setup to a cri-o based k8s setup. This will mainly include doing a lot of research and try to find out the differences and how to transfer all the stuff without much downtime. It might also include some tooling effort.

There is a tool called caff, which is the de-facto standard when dealing with keysigning (on a large scale, e.g. after a key signing party). This tool hasn't been touch in years, is written and configured in Perl (hence cannot be read and/or maintained :smile:) and is not easy to package, because of a lot of dependencies, etc. It is not even available in our default repositories (at least for Tumbleweed). In general there seems to be a certain kind of frustration with this software, but there is no real alternative available yet. Ideally the new toolset should allow to organize a complete keysigning party, e.g. it should assist the organizer with:

The problem I typically find very hard to figure out in the whole SUSE company who is the go-to guy for a certain skill/knowledge/experience. I'd like to have some place where one, who does not know people around him, can just browse and search for people by some tag or label. Sometimes you have a problem in a specific area but you don't know who to ask to, or even if you do, you don't know there were many other people with the same knowledge/experience you could have ask before.

I'm currently using urlwatch to watch for new releases in upstream projects. It monitors the output of a URL and notifies you about any changes. This works fine for URLs, but there is currently no official support for GitHub. Due to the nature of the GitHub webpages, there is a some change each time you access the page and it is difficult to come up with the right set of filters. Since there is an official API that can be used to ask for changes in a particular repository, it would be nice if urlwatch had support for it. I've worked on a prototype in the past, but never came around to cleaning it up, and making it configurable through urlwatch's configuration files. Upstream is interested in this feature and is willing to merge it.