[Pulp-dev] Pulp Installers Team Meeting Minutes 2020-11-04

[Mike DePaulo]

## November 4 Agenda
* https://pulp.plan.io/issues/4968
  * Good ramp up task for Pavel
* Triaging process - up to #6747
* We spent most of the meeting going through open pulp_installer PRs

-- 

Mike DePaulo

He / Him / His

Service Reliability Engineer, Pulp

Red Hat 

IM: mikedep333

GPG: 51745404

___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Katello/Pulp3 Integration mtg

[Grant Gainey]

November 4, 2020

Overview

   -

   Katello Schedule
   -

  3.18 branching:  Nov 2nd, Targeting Pulp 3.7
  -

 PRs are open, process is starting


Pulp

   -

   Pulp2
   -

  2.21.4 GA happened
  -

   Pulpcore
   -

  3.9 still on track for Nov 30
  -

 https://pulp.plan.io/issues/7789
 -

  Alternate Content Sources feature planning
  -

 Met w/ jsherrill, mminar, and bbuckingham, bmbouter to write a
 plan, then katello and pulp to estimate level of efforts
 -

 Headed for katello 4.0
 -

   RPM
   -

  Various fixes, including the correct handling of changed repo
  metadata without a revision bump.
  -

  Pulp folks are supportive to prioritise the mirror-rpm-metadata
  feature for Katello 4.0.
  -

 https://pulp.plan.io/issues/6353
 -

 We’ll try, but it’s not clear whether we have enough capacity for
 it.
 -

   Migration
   -

  Memory issues seem to go away with memory leak fixes in creatrepo_c
  -

 https://github.com/rpm-software-management/createrepo_c/pull/231
 -

 https://github.com/rpm-software-management/createrepo_c/pull/233
 -

 Not merged or released yet, but createrepo_c folks are asked to
 prioritise this upstream
 -

  Customer-like repo testing
  -

 1K+ repos, ~300K rpms, 600K+ errata relations and other smaller
 content types
 -

 Initial run - 7 hours for pulp, 9 hours (including pulp) for the
 rake task with reimport_all=true
 -

  Priorities for tasks or painful bugs
  -


 https://www.redhat.com/archives/pulp-dev/2020-November/msg2.html
 -

 Let me know if katello opinion on priorities differs
 -

  Migration from scratch, in progress
  -

 https://pulp.plan.io/issues/7714
 -

  Potentially a need for another 2.21.z release to add indices to mongo
  to the content collections.
  -

 ggainey cries in release-nanny
 -

  Has katello started integration with progress reports?
  -

 What is the priority for fixing the uniqueness of the `code` for a
 progress report https://pulp.plan.io/issues/7732
 -

  Pulp_deb https://github.com/pulp/pulp-2to3-migration/pull/149
  -

 Recently updated, seem to be a work in progress
 -

 Is there a known deadline to include it in Katello?
 -

   Ansible
   -

  0.5.0 was released. Has the url format change
  -

  Katello’s 3.7 repo is being upgraded due to it being shared with
  Galaxy NG also
  -

 Trying to sort out how to avoid these rush upgrades in the future
 -

  We’re working on supporting more fields in requirements.yml

Katello

   -

   Capsule-sync optimization
   -

  Happening at katello end
  -

  Trying to get a test-box for metrics - results #soon

QE

   -

   Waiting on test-system to start premigration work


G
-- 
Grant Gainey
Principal Software Engineer, Red Hat System Management Engineering
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Pulpcore team meeting notes

[David Davis]

## November 3, 2020

### Previous action items
* [david] To send out last call for feedback before merging
https://github.com/pulp/pulp-ci/pull/737
* [david] schedule pulpcore FIPS meeting with bmbouter for later in November
* Done.
* [dkliban] file a task for running tests for multiple plugins in one fips
environment in the installer nightly
* [fao89] look at driving forward release automation
* [x9c4] to backport https://pulp.plan.io/issues/7737 and release 3.6.z
* In progress
* [dkliban] cherry-pick 'request' commit to 3.8 branch
* Abandoned since change is a feature
* [ipanova] open a doc bug re:don't use settings in the models fields
   *  done https://pulp.plan.io/issues/7776
* [daniel] revert data corruption issue
* done. also have PR for repair all repos api endpoint.

### Topics
* FIPS epic for pulpcore - https://pulp.plan.io/issues/3778
* Closed out, new issues to be filed as needed
* Release automation next steps
* Post-release steps (branching, bumping to dev versions, updating
template config, etc)
* Need a Pulp query that shows issues for pulpcore (filters out
installer, operator, etc)
* Have automation open all PRs at once? Makes it easy to have a
reviewer review everything together
* Installation of our fips patch to Django is not working reliably in pypi
and source installation
* ask mikedep333 to take a look
* docs day
* nov 23
* go/no-go meetings?
* when do plugins bump requirement when they need a pulpcore feature
* Bump the floor version when you merge the change that requires
pulpcore feature
* If you require a change in pulpcore master, bump the floor to dev
version
* Remove dev from pulpcore version when releasing a plugin

### Action Items
* [david] To send out last call for feedback before merging
https://github.com/pulp/pulp-ci/pull/737
* [dkliban] file a task for running tests for multiple plugins in one fips
environment in the installer nightly
* [fao89] look at driving forward release automation.
* Automate post-release steps (branching, bumping to dev versions,
updating template config, etc)
* [david] a Pulp query that shows issues for pulpcore (filters out
installer, operator, etc)
* [david] move django fips repo to pulp
* [david] schedule go/no-go for nov 24
* [x9c4] to follow up on mailing list with proposal for setting pulpcore
requirements for plugins

David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] CLI team meeting notes

[David Davis]

## Nov 4, 2020

* pulp_migration support?
* No plans to support the migration plugin
* User stories
* Not really helpful ATM. Write them if you need them.
* Dealing with lint/checks
* mypy and shellcheck are picky and require ramp up
* Factor extra time into estimates
* What we have so far
* Most pulp_file commands
* No content commands
* Lots of missing options (eg filters) and no help text
* Exporters
* Tasks
* Artifacts
* Orphan cleanup
* Stuff to do
* Help text
* Another plugin (rpm or container)
* Recordings
* ggainey to demo creating a cli command from scratch
* Possible mypy demo?
* Help text
* Can we grab it from the schema?
* david to file ticket (https://pulp.plan.io/issues/7787)

David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Travis pricing

[David Davis]

We looked at Fedora's Zuul instance before and decided against using it for
two reasons: (A) it'd be a lot of work/maintaince (eg we'd have to write
our own zuul jobs, bring our own compute resource, etc), and (B) we were
worried about the support since it's not a paid (or freemium) option.

That said, it might be worth considering again if nothing else for testing
on specific environments such as selinux which is difficult to do on hosted
CI providers.

David


On Tue, Nov 3, 2020 at 3:51 PM Neal Gompa  wrote:

> On Tue, Nov 3, 2020 at 3:35 PM David Davis  wrote:
> >
> > Travis recently announced changes to their plan pricing that will impact
> open-source projects such as Pulp[0]. It's likely that we'll exhaust the
> monthly budget that Travis is going to give OSS projects and we're not sure
> how generous Travis will be giving out extra build minutes.
> >
> > Given our concern, members of the CI team met today to discuss our
> options. We have some notes[1] from our meeting about some of the options
> that stood out to us. We'd like to have a plan in place when the new
> pricing gets rolled out to our organization.
> >
> > Any feedback is welcome.
> >
> > [0] https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
> > [1] https://hackmd.io/n6kStnNiTPGekAWGdNvbhA
>
> Could we use the Fedora CI Zuul instance[2]? There's already a ton of
> other projects using one of the Zuul instances on
> softwarefactory-project.io, and leveraging the Fedora CI
> infrastructure could also help future efforts in doing auto-release to
> Fedora for Pulp releases, too.
>
> [2]: https://fedora.softwarefactory-project.io/zuul/projects
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
>
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev