HackMDPulpCon 2023 Schedule
GOOGLE MEET LINK TO JOIN PULPCON
Welcome to PulpCon 2023!
We prepared 4 days of various sessions, including user, admin, dev oriented topics.
Missed anything? Watch a recording at the PulpProject youtube channel!
For speakers
In the schedule for your talk, please add* a link to your slides, notes, presentation, agenda or whatever you have and willing to share, so attendees could get an idea what your talk is about and also have some urls/commands handy if you share those.
* You need to be logged-in in order to modify this doc. If you are in the read mode, you should see the "Edit" button on the top right of the page.
Survey
Please complete this feedback survey after attending PulpCon this year.
Video links
Join us on Google Meet.
Lightning talks on day#1.
Interested in:
- sharing a quick update on your Pulp plugin/component?
- sharing a cool feature you used while developing your plugin?
- having more contributions to your Pulp component?
- anything else?
Give a lightning talk (5 mins) on day#1 of PulpCon, add your topic here.
Monday, November 6 (day #1)
GOOGLE MEET LINK TO JOIN PULPCON
* click on the start time to get the time in your time zone
| Topic | Speaker | Starts (UTC) | Starts EST | Starts CET | Duration (talk+Q&A) | Links |
|---|---|---|---|---|---|---|
| Welcome + audio/video/sharing check | ggainey + everyone | 13:45* | 8:45am | 14:45 | 15 mins | slides/agenda |
| Year in Review & Look Ahead | rchan | 14:00* | 9:00am | 15:00 | 25 mins | slides |
| Pulp Container Registry in Katello - Past and Future | iballou | 14:30* | 9:30am | 15:30 | 25 mins | slides |
| Pulp Domains and pulp_rpm | ggainey | 15:00* | 10:00am | 16:00 | 25 mins | slides/agenda |
| Pulp Maven Demo | dkliban | 15:30* | 10:30am | 16:30 | 25 mins | slides/agenda |
| Drinking my own champagne. My personal use of Pulp | decko | 16:00* | 11:00am | 17:00 | 25 mins | slides/agenda |
| Lightning talks | anyone | 16:30* | 11:30am | 17:30 | 30 mins | slides/agenda |
* Any time left before 17:00 UTC/ 12:00pm EST/ 18:00 CET can be used for open discussion
Tuesday, November 7 (day #2)
GOOGLE MEET LINK TO JOIN PULPCON
* click on the start time to get the time in your time zone
| Topic | Speaker | Starts (UTC) | Starts EST | Starts CET | Duration (talk+Q&A) | Links |
|---|---|---|---|---|---|---|
| Support for Flatpak in Pulp | sberg | 14:00* | 9:00am | 15:00 | 25 mins | slides |
| **Pulp at Microsoftg [WON'T BE RECORDED] | davidd | 14:30* | 9:30am | 15:30 | 25 mins | slides/agenda |
| OpenTelemetry with Pulp. Now what? | decko | 15:00* | 10:00am | 16:00 | 25 mins | slides/agenda |
| A Year of Data | bmbouter | 15:30* | 10:30am | 16:30 | 25 mins | slides/agenda |
| Installing Pulp Operator in k8s with different methods | mikedep333 | 16:00* | 11:00am | 17:00 | 50 mins | slides/agenda |
* Any time left before 17:00 UTC/ 12:00pm EST/ 18:00 CET can be used for open discussion
Wednesday, November 8 (day #3)
GOOGLE MEET LINK TO JOIN PULPCON
* click on the start time to get the time in your time zone
| Topic | Speaker | Starts (UTC) | Starts EST | Starts CET | Duration (talk+Q&A) | Links |
|---|---|---|---|---|---|---|
| Container deployments & migration from Pulp 3 Ansible Installer | mikedep333 | 14:00* | 9:00am | 15:00 | 25 mins | slides/agenda |
| HA Deployment of Pulp on Kubernetes Demo | dkliban | 14:30* | 9:30am | 15:30 | 25 mins | slides/agenda |
| Multi Geography Pulp Architectures | bmbouter, ipanova | 15:00* | 10:00am | 16:00 | 25 mins | slides/agenda |
| Balancing Act between Services and Products | x9c4 | 15:30* | 10:30am | 16:30 | 25 mins | slides/agenda |
| Workshop: Ready to use Pulp CI jobs for everyone? [WON’T BE RECORDED] | quba42 | 16:00* | 11:00am | 17:00 | 60 mins | Initial hackmd Agenda |
* Any time left before 17:00 UTC/ 12:00pm EST/ 18:00 CET can be used for open discussion
Thursday, November 9 (day #4)
GOOGLE MEET LINK TO JOIN PULPCON
* click on the start time to get the time in your time zone
| Topic | Speaker | Starts (UTC) | Starts EST | Starts CET | Duration (talk+Q&A) | Links |
|---|---|---|---|---|---|---|
| Pulp Sub-repository Discussion Session | quba42 | 14:00* | 9:00am | 15:00 | 25 mins | hackmd discussion document |
| Building Pulp RPMs with PEP-517 compliant packages | odilhao | 14:30* | 9:30am | 15:30 | 25 mins | slides/agenda |
| Import/Export in Katello | parthaa | 15:00* | 10:00am | 16:00 | 25 mins | slides/agenda |
| Performance pitfalls and how to recognize them | dalley, gerrod | 15:30* | 10:30am | 16:30 | 25 mins | slides/agenda |
| Open discussion "Pulp Pain Points" | everyone | 16:00* | 11:00am | 17:00 | 60 mins | slides/agenda |
Friday, November 10 (day #5)
GOOGLE MEET LINK TO JOIN PULPCON
* click on the start time to get the time in your time zone
| Topic | Speaker | Starts (UTC) | Starts EST | Starts CET | Duration (talk+Q&A) | Links |
|---|---|---|---|---|---|---|
| Discussion of the topics identified during PulpCon if any | everyone | 14:00* | 9:00am | 15:00 | 3h | See Parking lot below |
Parking lot
Here is a place to park discussions that would be nice to have later:
- [discussed #2] Are there plugins, that reuse publication artifacts across publications?
- Background: For pulp_deb the time to generate package indices (metadata files generated by pulp_deb during publication) is a significant part of the total time for a standard sync + publish workflow.
- Often the previous repo version has already been published, and only a few new packages have been added since then.
- The Idea is to re-use the package index publication artifact from the previous version, and just extend it by the newly added packages, rather than regenerating the entire thing from scratch.
- The idea theoretically will work, but it will have lots of stumbling blocks to overcome along the way.
- [discussed #4] Strategic Project Discussion
- What medium-to-large project-wide activities can Pulp undertake to create more value for existing users or add new users?
- For example:
- audit the testing we have project-wide and then make it better
- bring all of the docs sites into one site
- What's the most strategic goal?
- Options:
- Bringing in new users?
- Helping existing users?
- Having existing who use certain plugins also use other plugins?
- What's the best return on our time investment?
- Some new users don't know about artifact distribution, others already do because they use proprietary competitors
- Latter would be served by migration instructions
- [davidd] As an existing user, Pulp has served them well and it's been stable.
- Issues have been worked around successfully.
- So focus on acquiring more users.
- [ipanova]
- Some new users cannot migrate to Pulp because there's some missing features
- Some new users may not be aware of our existing features. Blog writing perhaps?
- it seems that there is an agreement on the need to acquire new users, more promotion of project is needed
- it does not mean that we will only write docs and blog posts but it is a tech debt we would need to address
- gap analysis to see what prevents users to move to pulp from other similar projects, incl. a migration
- implementation of those gaps
- [lubos] More consistency with feature support rather than new content types. Like all default plugins support domains.
- [bmbouter] Add a table to the website with the list of plugins and their features?
- [bmbouter] The main advantage to Pulp (compared to other open source) is that it supports all different content types
- It's easier to get users who understand the value of an artifact repository than those who do not already
- Options:
- [discussed #1] Safely cleaning up content/repo versions (davidd)
- Problem: we need to clean up old repo versions, their publications, and content
- But those repo version/publications might be distributed
- More info: https://github.com/pulp/pulpcore/issues/2705#issuecomment-1351364685
- If you publish a repo version and distribute it, if a user changes it, it can be deleted by retain-repo-versions setting
- If the publication gets deleted, the distribution will be left pointing to nothing
- Solution: We'll protect distributed repo versions from automatic deletions when retain-repo-versions is set
- [discussed #3] Continuation of quba42's "subrepository" discussion
- [discussed #5] Single docs site discussion from yesterday
- Can Pulp move away from setup.py to PEP-517 build processes?
- "dev env" comment from https://hackmd.io/@pulp/pulpcon2023_pain_points
- potentially resolved by improving docs
- currently no specifics from davidd
- Let's talk about Shared Goals as a project
- docs
- dev-setup
- user-experience
- ???
- [mikedep333] Parking Lot should be renamed to Rail Yard
- -your topic and relevant context here-
