As you probably know, there is annual convention called Flock. This year’s is happening in Cape Cod, Hyannis, MA and will begin the morning of Tuesday, August 29. Sessions will continue each day until midday on Friday, September 1.
I have asked all of the session leaders from Flock some questions.
And now you are about to read one of the responses.
Multi-Arch Container Layered Image Build System by Adam Miller
What does your talk focus on?
My talk will focus on the Fedora Layered Image Build System (FLIBS), the challenges multi-arch has brought to the container ecosystem, how we will integrate FLIBS with other Fedora initiatives, and what this all means for Fedora users and contributors.
Without giving too much away, what can attendees expect to learn or do in your session?
They will learn how we will deliver multi-arch containers to our users from start to finish.
Who should attend?
Anyone interested in container technologies on architectures other than just x86_64 or interested in the future of building container content in Fedora in general. I welcome users and contributors alike.
What is the goal of your session at Flock?
My goal of this session is to education Fedora Users and Contributors of our initiative to build Fedora content using container technologies in respect to hardware architectures beyond that of just x86_64. We will also walk through the design of the system that has been built as well as discuss future plans to enable contributors to deliver to users more rapidly and with more flexibility.
What does it affect in the project?
Fedora Layered Image Build System (FLIBS) is driven primarily by the Fedora Atomic Working Group in order to provide a full-stack “containerized” Fedora from bare metal to application runtime, using container technologies. The Atomic Host being the operating system and lowest level of the stack, and the container images to be used at runtime being further up the stack. Our goal is to offer Fedora building blocks for every step of the way.
This also touches on Fedora Modularity, Factory 2.0, and Fedora CI in various ways as there are plans to allow Modules to be shipped optionally as containers in the future, we’re going to leverage features of Factory 2.0 in order to keep our content delivered to users constantly up to date, and we will be integrating with the Fedora CI effort in order to ensure the quality of that content we want to more rapidly ship before actually doing so.
What do you do in Fedora/how long have you been involved in the project?
I have been a contributing member of the Fedora Project since 2008. I’m a Packaging Mentor, a Proven Packager, a member of Fedora Release Engineering, a member of the Fedora Atomic Working Group, and an elected member of the Fedora Engineering Steering Committee since the Fedora 24 Cycle. Also, I’ve been on the Fedora Engineering Team at Red
Hat since April 2015.
What attracts you to this type of work or part of the project?
I find container technologies fascinating and I believe them to be the future of how we manage infrastructure, as such I would like to help Fedora work towards the goal of continuing to be Leading Edge and participate heavily in delivering those technologies to our users.