Between 29 August and 1 September I attended, with other folks from Brno, the FLOCK conference, which took place in Cape Cod, Massachusetts. Flock 2017 is over, but a lot of talks will stay in our memories. The talks were exciting, fantastic, and simply awesome. Also, it was my first visit to the USA.
I attended several talks and I would like to mention some of them. Especially, I would like to write about the following talks and workshops: “Factory 2.0, future and Fedora”, “Fedora Legal”, “Gating on automated tests in Fedora – Greenwave”, and “Let’s create a test for modules/containers”.
Let me briefly introduce what the talks were about.
Flock 2017 – Keynote
The Flock began with a keynote presented by Matthew Miller. His presentation provided a brief summary across all Fedora versions. Matt showed several graphs about active community folks and the feedback, which was gathered from Fedora 25 and 26 releases. He highlighted Fedora Atomic CI and Modularity as one of the two current objectives for Fedora. After Matt’s presentation, the presenters had a two-minute introduction to their talks. This was useful to get a picture of presenters and helped me to plan attending talks and workshops that I wanted to focus on.
Factory 2.0, future and Fedora talk
Factory 2.0 team delivers several tools that automate things in the Fedora world. The tools provide a way to automate the distribution of modules, and they are used for testing, building, and updating.
Let’s have a brief look at them.
WaiverDB is used together with ResultDB to record waivers against test results.
The service runs tests and the maintainer can waive it so that it does not block the other tests. The service is used together with Greenwave.
Greenwave is a service used to decide whether a software artifact can pass certain gating points in software delivery workflow. The policy defined by Greenwave defines which tests must pass in order to move to a new state.
Bodhi is a system that triggers and stores builds. The Factory 2.0 team enhanced Bodhi in order to display results from Greenwave and they also added the support for module updates, which are a part of modularity
ODCS is an abbreviation of “On Demand Compose Service”. This service can be used by other services and it updates docker images with the latest updates.
Factory 2.0 announced the support for chain rebuilds, which are important from the modularity point of view. The service responsible for chain rebuilds is called freshmaker.
Freshmaker, which waits for new fedmsg messages, is a new tool handled by Factory 2.0 team. Freshmaker is used mainly by module-build-service (MBS), which looks after modules delivered by the modularity team or Fedora module maintainers.
Fedora Legal – talk
Tom Callaway talked about legal aspects. The talk was fantastic, insightful, and full of information about software licensing. One of the important slides brought information about software patents that will expire soon, and thus the software can be used for Open Source. Tom also talked about why software should be safe and stressed that Fedora needs to remain free, which is awesome.
Gating on automated tests in Fedora – Greenwave – talk
Greenwave is a service for deciding whether the software with artifacts can pass some import points in the software delivery pipeline.
The results generated by Greenwave are stored in WaiverDB.
The checks that can be enforced in the pipeline are:
* dist.abicheck – it checks for ABI/API compatibilities
* dist.rpmdeplint – it checks for errors in RPM packages in the context of their dependency graph
* dist.updradepath – it checks whether the upgrade path was broken or not.
How to add tests to your packages – workshop
This workshop brings more issues for CI tests as well as for Module-Testing-Family (MTF).
The workshop tried to test several packages by Ansible. I tried to do it with MTF
and it worked as expected, but the artifacts were missing.
Let’s create a test for your module/container
This was a workshop presented by Jan Scotka and me. In 20 minutes we presented a brief overview of what MTF does, how it works, and some basic tests. Later on, the attendees had a chance to write tests for their containers. Some of them managed to make it. During the workshop we received a positive feedback about use cases for MTF, and of course what our plans in the future are, like testing containers in OpenShift. Good point, raised by Jan Kaluza, was to include some examples how to use MTF for several test multiple-host scenarios into our documentation.
What to tell at the end. Flock 2017 was great event, which I have ever visited. There were several talks and several session during 3 days, which was fine, and after getting back to home, I slept around 15 hours.
Flock is over
And Flock 2017 is over, but Flock 2018 will be there soon……