After many years of online networking, we are celebrating Foreman’s birthday on-site again! Address: Conference room, Parkring 4, 85748 Garching, near Munich, Germany.
We will be celebrating from 10 a.m. to 4 p.m., with an open ending!
We invite everyone to participate in our Call for Papers (CFP). If you have an interesting talk in mind that focuses on the use and development of Foreman, Katello, or Pulp, feel free to send your suggestions to cfp@atix.de. As a token of our appreciation, ATIX is inviting speakers to a dinner the evening before the main event.
I wish I could be there in person! Are the presentations in-person only or remote as well? If they’re remote, I could probably get a demo in there for container push, which should be mostly developed by then. We could also look into doing presentations on any other topics if there are requests
My talk Foreman - a complete lifecycle management tool for desktops? was accepted!
This talk will take a look at Foreman’s capabilities which are designed as a complete lifecycle management tool for physical and virtual servers and how they transfer to desktops.
We will look into three use cases with the most simple being a virtual desktop used for testing and writing training material. The second are a number of training notebooks managed by our events
team running CentOS, reprovisioned and set up for specific trainings. A setup which evolved over many years adopting for newer hardware, operating systems, requirements and more. The third is based on a customer requirement moving from self-managed Ubuntu desktops to a more managed approach.
All this showed us that a Linux desktop is not totally different to a Linux server, but adds much more complexity than just adding a GUI.
In the end we want to answer the question if Foreman is ready for desktops and perhaps also if desktops are ready for Foreman!
CI in the Foreman Project: from Jenkins to GitHub Actions, lessons, problems, outlook
The Foreman project has recently moved big parts of its Ci to GitHub Actions, to allow better re-use of code between repositories, easier control of CI by repository owners and to reduce the maintenance cost
of infrastructure. As with any other migration, this was not painless, but we learned a lot, created many useful snippets and found more places for improvement.
In this talk I will share the benefits of this migration for developers, show how the created workflows can be used in other projects, but also highlight problems that GHA has over Jenkins and what we plan to do to fix these.
Thanks @Bernhard_Suttner and ATIX for hosting us today! It was great meeting the community again in-person!
I will try to find some time to do a proper recap from my side and perhaps also to bring my slides in a shape were I feel comfortable of uploading them (as I have as always the feeling they are do not provide enough content without me talking).
