Pulp UI working group forming

Announcements
#1

A working group is being formed to design and create a UI for Pulp. The goal of this group will be to start and produce a MVP plan.
Please post here if you would like to join this working group.

7 Likes
#2

I’m in, please

#3

I’m interested.

#4

Count me in.

#5

I’m interested too

#6

I’m interested too

#7

The first meeting for the group is scheduled - Sept 19th 4pm CEST.

The meeting notes will be posted here.

1 Like
#8

Attendees:

Agenda

  • Demo current state of UI
    • Access management - users, groups, roles
    • Task management - show tasks + starting tasks
    • Ansible - repositories, remotes
  • PulpConf
    • starting tasks with options
    • fixing Access management
    • TBD
  • What could be also salvaged from galaxy UI - needs more investigation
    • Ansible - collections, namespaces, execution env., remote registries
  • Roadmap for 2025
    • RPM workflow
    • TBD

Repo: https://github.com/himdel/pulp-ui

bmbouters: add “available in oci-images” by PulpCON? (because ppl will want to start using it)

  • can pulp-team make this happen?
  • gerrod: reasonable - first step, “where is the code now?”
  • ggainey: oci-env profile would also be nice
    • bmbouters: trickier? because we’re not oci-env-profile-experts?
    • ask: Z/M familiar w/ oci-env? -yes - there’s already a galaxy-profvile, which uses the galaxy-ui
    • would love to see it in default-profile?
  • ggainey: how much work to get it into single-container-image?
    • gerrod: single-container: prob not that hard to add a new service to that image (as long as files/dependencies installed)
    • multi-container image - more work to get into the docker-compose
    • martin: auth in conatiners?
      • images default to basicauth
      • martin: POC authentication: basic-auth implemented, saves creds in browser (not very secure)

what’s the next step for this next week? How do we move forward?

  • Pulp-ui into pulp org on github
    • why? -less friction, users find it where they expect it
  • q: how do we release this?
    • automation - release to npm?

ordering: gerrod opens oci-img issue, work w/ M/Z to get repo into pulp-org, ggainey schedules next meetings, by next mtg

#pulp-dev in matrix would be the best communication channel

Action items

  • AI: [Martin] let’s get a CfP entry into discourse thread please
  • AI: [ggainey] repo into pulp-0org, give zita/martin admin privs on it (need repo-privs on himdel’s repo)
  • AI: enable UI in oci-images-all-in-one (gerrod?)
  • AI: M/Z to investigate automating npm release process
  • AI: [ggainey] schedule 30-min week til PulpCON

Next mtg: 26-SEP 0930 ET

2 Likes
#9

Sep 26, 2024

Attendees: ggainey, x9c4, mhradil, gubben, pbrochado

Prev action-item review

  • AI: [Martin] let’s get a CfP entry into discourse thread please
  • AI: [ggainey] repo into pulp-org, give zita/martin admin privs on it (need repo-privs on himdel’s repo)
  • AI: enable UI in oci-images-all-in-one (gerrod?)
  • AI: M/Z to investigate automating npm release process
    • PR open setting up most of it
  • AI: [ggainey] schedule 30-min week til PulpCON
  • AI: ggainey to post minutes (Pulp UI working group forming - #8 by ggainey)

Agenda:

  • Already community/external interest
    • Specifically, “UI page that would show all repositories containing a specified piece of content”
  • How are we going to consume npm image? (just install? src?)
    • Galaxy NG does it This Way : https://github.com/ansible/galaxy_ng/blob/master/setup.py#L22
    • How does UI get instantiated after?
      • Collect-static and installed under Pulp
    • What’s the ui GH workflow
      • Tarball uploaded as github release
      • setup.py in Gal/NG pulls dwn that tar.gz
      • Pypi contains/installs that tar.gz and issues collect-static to put the right things in the right places
    • Static files can be served by nginx directly
    • Proposal:
      • In oci-images repo
        • Download src
        • Run install/webpack
        • Configure nginx to serve them?
      • Sounds “reasonable”
    • Github artifacts - attached to a release (which is just updated (currently))
    • Would be nice/good to have specific releases in oci-image
      • Do NOT want branches yet (still way early days)
      • Maybe YYYYMMDDHHMM?
        • Maybe 0.0.yyyymmdd
        • maybe just 0.0.N
      • Mostly want to be able to know exactly what is/was running in an image when there is a problem
    • Mdellweg has done some similar things on a diff project - will point gubben at his experiences
    • Q: containers are “production ready” - is this a concern?
      • Prob not
      • None of the code added runs on the container - it’s all in the browser
      • UI is marked as “very tech preview”

Action Items:

3 Likes
#10

Oct 3, 2024

Attendees: mhradil, gubben

Prev action-item review:

Agenda:

4 Likes
#11

Oct 10, 2024

Attendees: ggainey, x9c4, mhradil, bmbouters, gerrod

Prev action-item review:

Agenda:

  • Started detecting-enabled-plugins and only showing appropriate section
  • Rpm-package-list basic functionality turned on
  • Mdellweg: status of being in images?
  • Gerrod: Q: tarball has a few static-files for nginx to serve.
    • How are variables in cfg set?
    • How can we change them?
    • Mhradil: set in API - if more is needed, will need to move away from static-build
    • Gerrod: any way to read these values from file built as part of pulp-oci-images-build? (a number of pulp-settings can be changed in ways that will affect the pulp-ui)
    • Mhradil: needs investigation, no obvious way to make webpack app do this
    • Mdellweg: changing API root - can’t expect UI to figure that out, addressing this is lowest-possible-problem
      • But there are other settings that need to be thought about (ie, domains)
    • Mhradil: could add .json cfg-artifact to allow these kinds of changes
    • Gerrod: where this workflow is happening : https://github.com/pulp/pulp-oci-images/blob/latest/images/s6_assets/template_nginx.py
    • Investigation needed, but sounds like there are some fruitful paths
    • Ggainey: can we shoot for being able to modify one thing (api-root?) from a cfg-file, as a way of proving the workflow
    • bmbouters: sounds like we are on-track for users to be able to see this in one-container-img by pulpcon
  • AI: mdellweg: get pulp-ui up and running in his dev-env
  • Mhradil may be missing next week

Action Items:

  • mdellweg: get pulp-ui up and running in his dev-env
  • ggainey: get pulp-ui up and running in his dev-env
#12

I am also interested

1 Like
#13

Hi there @thesubmitter - apologies, I failed to get back to you on this :frowning: The UI Working Group is meeting every Thurs at 1300 GMT, for 30 minutes. Drop me your email and I will add you to the invite!

Note that this “Phase 1” working group will only be meeting twice more - but part of the last mtg is deciding what a going-forward roadmap looks like, so there may well be a Phase 2 working group coming from it :slight_smile:

#14

Oct 17, 2024

Attendees: ggainey, zita, gerrod, pbrochado

Prev action-item review:

Agenda:

  • Gerrod: Draft PR for getting pulp-ui into Pulp’s OCI images
    • AI: [all] Review and comment on possibly better ways to store/serve files
  • Proposal:
    • Declare Phase 1 of UI Working Group at Virt pulpCON 1st wk November
    • Meet (email?) afterwards on putting together a Phase 2 WG
    • Seems to be acceptable to consensus!
  • Task-management work continues
  • Rpm-plugin work continues
  • “About” page being finished up
  • [zita] Add more or stabilize?
    • Task schedules API? - prob not very useful
    • [gerrod] Pulp_file workflows would be nice
      • Already discussed w/ Martin
      • Main Three: Upload, Sync, Publish/Distribute
    • [zita] Collections/Namespaces in Ansible
      • Last thing we can get “for free” from existing Ansible code
    • [ggainey] Important to have minimal friction in the “get up and running with the UI” docs/workflow
  • lmjachky/mhradil discussion last week?
    • AI: ggainey to nag Lubos to open issues
  • Pbrochado: docs onto main doc-site?
    • Unify now? Or wait for PulpCON?
    • Is there enough to make it worthwhile?
    • AI: [pbrochado] to get PR submitted
    • [zita] docs/UI needs to have LARGE WARNINGS/BANNER that user/pwd still saved into local storage on user-system
    • AI: [zita] check w/ mrhadil that this is still the case

Action Items:

  • [all] Review and comment on possibly better ways to store/serve files
  • [ggainey] nag Lubos to open issues RE starting up
  • [pbrochado] to get PR submitted for getting UI page into main-docs-site
  • [zita] check w/ mrhadil RE current-state of local-credential-storage
#15

October 24, 2024

Attendees: ggainey, pbrochad, mhradil, zita

Prev action-item review:

Agenda:

  • Authentication-stored-on-client
    • May not be any way around local storage?
    • [gerrod] Session-auth turned on by default?
      • Drf browsable API uses session-auth - maybe we can reverse-engineer this?
  • Pulp-ui into oci-images PR
    • Some tweaks still to do, but about ready to merge
    • Some env-var-naming details
    • Are we picking the right location for the static content? (now in pulp’s /static/ dir)
    • Prob w/ /static/ dir is, pulpcore manager collectstatic –clear would blow up the UI
      • Prob OK for initial-release
    • Mhradil says “looks ok to me” :slight_smile:
    • AI: [ggainey] to review by end-of-week
  • Pulp-ui open PRs - assign reviewers?
  • Mhradil: cookie-based auth question
    • Is there a Pulp API endpoint that will tell you who you are?
      • No, alas
    • AI: [mrahdil] open a pulpcore issue requesting a “who am I?” response
  • AI: mrahdil working on pulp_file workflow - review next week!

Action Items:

  • [ggainey] review pulp-oci-images PR by end-of-week
  • [mrahdil] open a pulpcore issue requesting a “who am I?” response
  • [mrahdil] working on pulp_file workflow - review next week!
1 Like
#16

October 31, 2024

Attendees: zita, mhradil, ggainey, gubben, mdellweg, pbrochad

Prev action-item review:

Agenda:

  • [mhradil] report on pulp_file
    • Still in progress
  • PulpCon
    • phase two post on forum?
      • What would a phase2 mtg schedule look like?
      • What would a good target be for completion?
      • How long should we think about it taking?
      • [zita] we should have this discussion at PulpCon and get community input/buy-in instead of answering these questions today
    • Presentation
  • [gerrod] Needs help w/ pulp-oci-images PR
    • CI isn’t working even tho works locally
    • [ggainey] try to test locally/investigate today
    • Discussion ensues
  • Quick demo of current-state of mhradil’s work
    • Should we hide not-yet-working tabs?
    • Discussion ensues
      • Setting expectations is the important thing
      • “Current state” can go into images, as long as we label it appropriately
        • Banner on every page “THIS IS DEV-WORK IN PROGRESS!”
        • Specific boilerplate-only-so-far pages have specific warning
        • Maybe link to github repo when asking for PRs :slightly_smiling_face:

Action Items:

  • [image][ggainey] review/investigate gerrod’s PR
  • [image][ggainey] post minutes, and officially close Phase I thread in discourse
  • [mhradil] add “DEV WORK IN PROGRESS” warnings to UI pages
#17

Hello all,

The current Pulp-UI working group has declared “Phase I” to be “done”. Martin Hradil will be presenting the current state of the work at PulpCon next week!

At that presentation, we’ll be discussing details around a Phase II of this effort. If you have Opinions, please let us know! Once we have gathered people’s thoughts, we’ll put a post up here with the Phase II proposal going forward, and then carry on.

Hope to see you at PulpCon next week!

2 Likes