HackMD
2022 Open Floor/Triage Minutes
December 20, 2022
- core/3.22 released! Thanks ipanova!
- Cancel next week's meeting?
December 13, 2022
- December 3.22 release https://discourse.pulpproject.org/t/3-22-release/719
- How to sync-then-publish? https://github.com/pulp/pulpcore/issues/3452
December 6, 2022
- quba42: Need help assessing https://github.com/pulp/pulp_deb/issues/690 since I don't know enough about orphan cleanup.
November 29, 2022
- pulpcore 3.22 tentative GA date is scheduled for Dec 5th
- CodeQL checks in github
- do it, or not?
- if "do it" - we need to actually look at and address all findings
Oct 25, 2022
- Will there ever be a feature like this? Does it need/have a ticket?
- ggainey responded for pulp_rpm - no current plan, asked for a Feature ticket to be opened to continue the discussion
- hstct for pulp_deb maintainer
- bmbouter to work w/ quba42 to make this happen
October 4, 2022
- https://discourse.pulpproject.org/t/support-zero-downtime-updates/645/4
- We've started planning this work and will have a GitHub issue soon
September 27, 2022
- Proposal advertisement: Remove the single commit check from the CI and use Squash merging
- Should pulp_deb issues appear on the new Pulp Kanban board? See also this GitHub PR comment.
- CfP for PulpCon is due today. Do we want to extend it till Monday? I see only one Pulp team member as a speaker among the proposed talks. https://discourse.pulpproject.org/t/pulpcon-2022-call-for-proposals/590
September 20, 2022
- Plugin writers please broaden and declare your dependencies, see these docs
- Container Based Pulp Install Next Steps (FYI):
- Moving the operator images to be built in pulp-oci-images repo (all container builds will live in that repo)
- Operator images will likely become the images we recommend for use, while the single container is more for trying out all of the plugins
- Operator images will replace ansible build with a docker file so users can more easily build the containers locally
September 6, 2022
- [lmjachky, ewoud] Is it worth publishing bindings on a daily basis?
- The bindings for clients are built daily and published on PyPI (even when no change was recorded).
- Does it makes sense to store the bindings in GIT repositories for the sake of the history and publishing?
- it would become a new nightly process to import bindings into GIT; then, have a GH action to publish a nightly package if there was a new commit created
- that could allow us to determine if a new release is needed
- [quba42] pulp_deb Nightly CI/CD failing on "publish" step:
- [dalley] UUID generator wrapper https://github.com/pulp/pulpcore/pull/3136
August 30, 2022
- Release pulpcore 3.21 go/no-go
- Can we think about adding a "context report" feature to Task, that could be used to report specific-task-request info back to the invoker? Examples:
- quba42's Store sync-options on task
- wibbit's pulp_rpm copy dry-run request
- FYI: pulp-smash proposal to be put into read-only mode on Sept 5th
August 23, 2022
August 2, 2022
- pulpcore 3.18 release today?
- yes
- Can we find a naming consensus for https://github.com/pulp/pulpcore/pull/2999#issuecomment-1202674644
- The provisional consensus for the name is
info.
- The provisional consensus for the name is
July 26, 2022
- Should we relese pulp_file this week?
- yes, we should. x9c4 will do the release
July 19, 2022
- Can we remove the Required PR machinery from the CI?
- Or at least mark a PR using it as not ready to ship.
- Solution: There should be a test to prevent PR's to merge before all the required ones are merged.
- Or at least mark a PR using it as not ready to ship.
- Should we assume that tests always run on the same box as pulp services
July 12, 2022
May 31, 2022
- [lmjachky] Why do not we ship signing scripts with plugins when the only required fields that are set by administrators are basically a keyid, gnupghome, and name of a signing service?
- If we strictly define the interface, signing utility (gnupg), and environment variables (administrators should in no way touch the environment variables) of a signing script, does it still make sense to allow them to write their custom scripts?
- In the end, we will have just one pulp-provided script referenced from multiple signing service instances where each instance differs from the other by a keyid, name, and potentially gnupghome.
May 24, 2022
- pulpcore 3.20 release date
- June 14th!
- introduction Tobias (hstct)
- pulp_deb tests are broken on master with:
pulp_smash.pulp3.bindings.PulpTaskError: (PulpTaskError(...), "Pulp task failed (DeclarativeArtifact must not provide both 'url' and 'urls')")- See: https://github.com/pulp/pulp_deb/runs/6566690326?check_suite_focus=true
- see https://github.com/pulp/pulp_python/pull/536/files on how to fix
- Cannot run local tests on freshly built
pulp3-source-fedora35(pulp_installer, pulpcore, pulp_rpm, pulp_deb all from latest main branch):ImportError: cannot import name 'OrphansApi' from 'pulpcore.client.pulpcore' (/usr/local/lib/pulp/lib64/python3.10/site-packages/pulpcore/client/pulpcore/__init__.py)
May 17, 2022
- Ingest by url?
April 26th, 2022
-
[lmjachky] Assigning GH issues to myself is very cumbersome. All pulp contributors should be allowed to assign themselves to any issue within any pulp repository.
- In order to enable assignments, one has to have write permissions to a repository.
- Should we enable all people inside the Pulp organization to have write permissions: https://github.com/orgs/pulp/people?
- In order to enable assignments, one has to have write permissions to a repository.
-
[lmjachky] What is the status for sprint planning dashboards that should replace the boards available at plan.io: https://github.com/orgs/pulp/projects?type=beta?
- Can we at least start using GH Project Boards similarly to pulp_ostree: https://github.com/orgs/pulp/projects/7?
-
[quba42] How to deal with https://github.com/pulp/pulp_rpm/issues/2501 (as far back as pulp_rpm 3.9 for Katello 2to3 migrations)?
April 12, 2022
- Checking the
post_docs_test.shI understand that they are meant to ensure that the documented examples work as expected. I'm not sure if this is valid, but what if we added the steps to remove/clean the "objects" (content, repository, distribution, etc) in the documentation workflow (this way, we would cover the entire "lifecycle" workflow of a plugin) andpost_docs_test.shscript as well?
April 5, 2022
- FYI some discussion on the goal of making tests independant of all other tests
March 29, 2022
- "Release Day"
- releases are 'easy', but still take up time/spoons
- can we declare releases to all happen on one day of the week?
- how about Tuesday?
- Yes, let's try to do this!!!
- how about Tuesday?
March 22, 2022
- It may come up in triage anyway, but I was wondering what the plan for the following issue is: https://github.com/pulp/pulp_rpm/issues/2422
- I originally found it via: https://bugzilla.redhat.com/show_bug.cgi?id=2024963
March 15
- https://github.com/pulp/pulp-oci-images/issues/161
- Any way to prioritize this/add to sprint?
March 8
- 3.19.0 release date. How about April 12?
March 1
- What should a user do to avoid certificate errors when serving content from a distribution within the pulp:latest image via HTTPS (maybe pulp_ostree specific)
- When accessing the content, the following error is shown: "Peer certificate cannot be authenticated with given CA certificate"
- Disabling TLS verification helps, but it is not a real solution if the user wants to distribute the content via the HTTPS schema
- Upcoming plugin_template breaking change
- The unit test runner is switching to pytest
- Will require several unit tests to be rewritten when applied.
- These tests mostly are all the same as they originally came from the plugin_template itself
- The pulpcore and pulp_file PRs should show how to fix
Feb 22nd
Feb 15th
- https://discourse.pulpproject.org/t/pulp-cli-usability-discussion/370
- options naming for pulp-cli
- FYI: please let bmbouter know if you see this error in the CI
- The failing test is
test_sync_https_through_http_proxythat fails like this
- The failing test is
- please read and provide feedback if any on the work that docs SIG has done https://discourse.pulpproject.org/t/pulp-docs-sig-findings-conclusions-software-repository-management/372
Feb 8th
- FYI run tests only in your nightly CI run with the
nightlypytest mark- Now on the plugin_template here.
- Here's an example of
pulp_ansibleusing it.
- New Prometheus metrics exporter built by the team supporting the internal PyPI (Thoth)
- https://github.com/thoth-station/pulp-metrics-exporter
- Very basic right now and current focus on python plugin stats
- They would appreciate us contributing to it as well
Feb 1st
- FYI a new
ptestis available in the vagrant env, use it to run the functional testsptestorptest pulpcorewill test pulpcoreptest <plugin_name>will run a plugin, e.g.ptest pulp_file- Later the unit tests will also be run with this too
- FYI new proxy tests are available
- pulp-smash has new fixtures so they will run nicely locally
- See pulpcore's tests as an example:
- Github - https://discourse.pulpproject.org/t/github-issues-and-labels/333/3
Jan 25
- CI: Replace docker with github registry
- For awareness, 3.18.0 tentative schedule https://discourse.pulpproject.org/t/pulpcore-3-18-0-release-schedule/330
- Proposal / Question: Can plugin teams have 1 person for 1 day try to port their plugin docs to use pulp_cli by Feb 4th?
Jan 18
- we've discussed how backport process, BZ re-integration is going to change after the move to GHI, let's talk some about triage process too. And sprint planning
- do we want a
tutorialsection on discourse, this potentially will be redundant depending on how we plan to re-structure docs https://community.theforeman.org/c/tutorials/23 - FYI two testing related things
- upcoming recording on how to adjust writing tests to use the new fixtures
- https://discourse.pulpproject.org/t/event-testing-pulp-using-the-new-pytest-fixtures/311
- please discontinue writing tests that inherit from unittest, instead use pytest
- parallel testing is now available in the CI
- https://discourse.pulpproject.org/t/parallel-test-runs-added-to-ci/320
- need unique fixtures still to make much more usable
- upcoming recording on how to adjust writing tests to use the new fixtures
- bmbouter's hope: All mini teams update plugin docs sites as if it's the only site your users will ever see
Jan 11
* Proposal: put old projects into read-only mode, e.g. Crane, Docker, Nectar, and Puppet Support
* https://pulp.plan.io/projects
* [done]
- we've discussed how backport process, BZ re-integration is going to change after the move to GHI, let's talk some about triage process too
- do we want a
tutorialsection on discourse, this potentially will be redundant depending on how we plan to re-structure docs https://community.theforeman.org/c/tutorials/23
Jan 4
- https://discourse.pulpproject.org/t/design-question-why-do-publications-not-have-a-unique-name/300
- 3.18 release date?
- Feb 8?
