Virtual PulpCon 2024 Call For Proposals!
Where?: Online!
When?: November 4-8, 2024, 0800-1200 GMT-5 (US ET)
CFP ends: Sept 30, 2024
CFP interest voting (if needed): Oct 1 - Oct 4, 2023
Virtual PulpCon is coming and we would like to welcome you and encourage to participate in any way you prefer, whether it’s presenting, active participation in discussions, or just listening. Similar to what we did for Virtual PulpCon 2023, we will host half-day sessions, with presentations recorded and made available on our youtube channel.
To propose a session for PulpCon 2024, please add it to the list below, along with your name. Add an estimated timeframe (25 or 50 min) for the session. Each talk should leave at least 10 min at the end (5 for Q&A and 5 for a break).
This CFP ends on September 30th. (We recognize that his is a relatively short CfP window - but we’re a bit late getting things organized this year, and the reality is that the vast majority of CfP responses come in either the first week of the window, or on the last few days.)
Some possible “themes” for talks:
- Lessons learned from production use of Pulp
- Experiences running Pulp “at scale” (i.e., large datasets, large number of client-consumers)
- What features do you use/not care about?
- What do you workflows look like?
- Experience with/thoughts on Pulp’s multi-user/multi-tenancy (domains) support
- Example: “Trust and ownership in your multi-user Pulp installation”
- Experience integrating with Pulp
- If you could have a brand-new API - what would it look like?
- What things would you wish Pulp did differently?
- “Lessons learned in 2023”
- both from the Pulp team and Pulp users!
For proposals, please define your “intended audience”, preferably with a focus on either “developers” or “users”.
NOTE : It’s fine to add a “rough idea” for a talk below, to be refined as we get closer to PulpCon!
If you have any questions/comments, feel free to add those as nested bullet points too.
Note that we plan to leave some timeslots open for topics that come up during the week of PulpCon.
Talk Proposals:
Template:
[Focus] "Title" - Intended duration - Speaker's Name
* short description
[USER] “Building bootable container images in Pulp” - 20m - TBD
- Give a quick intro about pulp-container image building machinery
- Run a demo showing how users can upload a Containerfile to Pulp and then build an image with it
- Boot a vm with the built container image
[USER] “Pulp UI - presenting a proof-of-concept UI” - 30m - Zita Pospisil Nemeckova, Martin Hradil
- Demo of the current state of the UI project, current limitations
- Current availability - how to try it out, contribute
- Discussion of roadmap, use cases, plans
[DEV] “Packaging Pulp RPMs 2024 Edition” - 20m(could be 50m if we want to talk about improvements) - Odilon Sousa
- This is the yearly talk about how Katello packages Pulp
- We improved a lot from last year with Dependabot, Nightly builds, Copr as build system and one Github Workflow that auto updates packages used by Pulpcore and it’s plugins.
- We will have graphs, charts and all the good stuff that devs love to see.
[USER] “The new Pulp documentation website” - 30m - Pedro Brochado
- Overview of the project design and the migration process
- A tour on how it looks today
- Discussion on further improvements and challenges
[USER] “What’s in Pulp’s Future” - 60 min - TBD
- What would/could/should a “Pulp4” look like - and how do we get there without a “big bang” upgrade?
[DEV] “Katello’s Content Future” - 25 min - TBD (@iballou as backup)
- Goal: Inspire innovation through a discussion about what the future of Pulp’s integration into Katello might look like.
- Topic ideas:
- The rise of bootc hosts
- Flatpak
- Increasing demand for highly-available Katello
[USER] “State of Domains in Pulp” - 20 mins - Gerrod
- Give an update on the state of the Pulp Domains feature since last year
- Give a tentative roadmap on extra features we plan to add
- Discussion around current domains usage and any feedback for future improvement
(This is a wiki post, and should be editable by logged in users.)