Pulp at CfgMgmtCamp

Fringe day:

• Pulp 4 discussion (wed?)

Talk ideas:

• Dennis:
  • Introduction to Pulp
  • Reflection Retrospective 2 yrs of services.
    • Pulp 4 forecast
• Matthias:
  • What's New in Pulp for Users
    • present the new website
      • markdown for easier contributions
    • present the UI
      • 5 years in the making and now we have a ui…
  • Pulp glue vs Bindings?
    • REST framework -> openapi 3.0.3 schema -> ???
    • Autogenerated Bindings
      • generated (no manual work; not really)
      • still corner cases
      • picky on versions
      • Availability in several language ecosystems
      • Heavily used in our integration tests
      • Used in some downstream ruby and go products
    • Glue
      • developed as part of the pulp cli
      • split out as a separate library
      • Version agnostic by design
      • Carries a set of version dependent hot fixes to api schema flaws
      • Hand crafted; handles tasks transparently
      • Can be augmented to perform higher level workflows
      • "converge"
      • Only available for Python
      • Used by pulp-cli, squeezer (still migrating), pulp replicate
      • Next target user: Satellite, Copr, your repo mgmt solution

Abstracts

What's new in Pulp?

It's been a year since we last met on CfgMgmtCamp.
In this talk we want to take a short tour to outline the most important user visible changes.
To this end we want to highlight specifically our revamped Website where all documentation for the project are now united.
Also we are proud to finally present a GUI.

This talk focuses on end users.

More than just duct tape: pulp-glue the sticky client library

Evolving from being a hidden abstraction layer inside of the famous pulp-cli, pulp-glue has been released as a separate independent library.
In this talk we want to discuss why we think this was worthwhile.
We specifically want to contrast the glue library to the existing auto-generated bindings.

This talk focuses on integrators and developers.