---
# System prepended metadata

title: Pulp/AH integration team meeting
tags: [Minutes]

---

# Pulp/AH integration team meeting

Old link for the pulp-container meeting notes
    * https://hackmd.io/z7i694VeTR-p4hgTk2Oocw

## Template
===========
## Date
### Action Items

### Priority List

### In the priority Queue

### Pulp
   - Pulp_ansible
   - Pulp_container
   - Pulpcore
### Galaxy
   - 

### Open PRs
  - want to talk, link a PR to the agenda


<!-- for the upcoming meeting, put your items in this section below (do not create a date title)-->
## Upcoming
===========
### Action Items
[someone] start a new hackmd
[davidN] schedule meeting for namespace sync planning


==========
## Oct 3rd
### Action Items
[someone] start a new hackmd - done
[davidN] schedule meeting for namespace sync planning - done

### Priority List

### In the priority Queue

- Can we cleanup this hackmd? 2k lines takes time to load.

### Pulp
   - Pulp_ansible
       - What is going on with namespace sync?
       - needs planning - it will be resurrected 
   - Pulp_container
       -  is it possible to upgrade to 2.14 branch instead? https://github.com/ansible/galaxy_ng/blob/stable-4.6/setup.py#L119
       -  Circular Import : https://github.com/pulp/pulp_container/pull/1084
   - Pulpcore
       - does this need to be backported and where? 3.21 https://github.com/pulp/pulpcore/issues/3124
       - [jjerabek] `write_only_fields` https://github.com/pulp/pulpcore/pull/3167 (see comment https://github.com/pulp/pulpcore/pull/3167#discussion_r985765137)
         - pulp team will need to do auditing
       - FYI pulpcon talk organized by bmbouter on "operating Pulp" want to collab w/ @awcrosby
       - reworking the operator and single container to be built on top of each other instead of totally separate build files
           - proposal: https://hackmd.io/8URyo-kXSWapHLfhyfNO2A
           - 
### Galaxy
   - [ttereshc] https://issues.redhat.com/browse/AAH-1323
       - to stop ping pong and agree what to do if anything
  - [awcrosby] Added a +1 to zero time updates: https://discourse.pulpproject.org/t/support-zero-downtime-updates/645
      - next step: to discuss some at Oct 4th pulpcore meeting
  - CI issue resolved?

### Open PRs
  - want to talk, link a PR to the agenda

===========
## September 26th
### Action Items
- list of "fast response branches"

### Priority List

### In the priority Queue

### Pulp
   *  Can we make a list of "fast response branches"?
   - Pulp_ansible
       - What are the branches we need to maintain in the CI?
           - https://github.com/pulp/pulp_ansible/pull/1261#pullrequestreview-1116883774
       - Removing single commit check
           - https://github.com/pulp/pulp_ansible/pull/1252
           - project-wide proposal: https://hackmd.io/SVCMjpwXTfOMqF2OeyyLRw
       - Galaxy PR to use collection upload refactor
           - https://github.com/ansible/galaxy_ng/pull/1463
   - Pulp_container
   - Pulpcore
   - 
### Galaxy
   - 

### Open PRs
  - want to talk, link a PR to the agenda

## 19. Sep. 2022
### Action Items

### Priority List
1. Collection signing (Bruno)
   - Deployed ; no more action items
2. Container signing (Bruno)
3. Move Ansible Namespaces to pulp ansible (higher prio)

### In the priority Queue

### Pulp
  - Pulp_ansible
    - 0.15.0 imminent
  - Pulp_container
    - few bugfix releases are out https://github.com/pulp/pulp_container/commit/527431b23fb55fc2c4a318b7b81080bfeb8b1167
  - Pulpcore
    - recommendation on how plugins should declare dependencies
      - https://github.com/pulp/pulpcore/pull/3176/files
### Galaxy
  - https://github.com/pulp/pulpcore/issues/3124

### Open PRs
  - want to talk, link a PR to the agenda

==========

## Sept 12th
### Action Items

### Priority List
1. Collection signing (Bruno)
2. Container signing (Bruno!)
3. Move Ansible Namespaces to pulp ansible (higher prio)

### In the priority Queue
- PoC: Repo Management - to implement collection content type (low-medium prio)
- David's wishlist

### Pulp
   - PulpCon https://discourse.pulpproject.org/t/pulpcon-2022-call-for-proposals/590
   - Pulp_ansible
       - PR review blocking additional work
           - https://github.com/pulp/pulp_ansible/pull/1176
           - https://github.com/pulp/pulp_ansible/pull/1178
           - https://github.com/pulp/pulp_ansible/pull/1237
           - Should we remove the slack nagware? It doesn't seem to be working.
           - What are the github nicks we should ping for reviews?
               - jerabekjiri
               - newswangerd
               - rochabruno
   - Pulp_container
       - import/export is feature complete for both sync/push repo types (will go into next feature release) 
   - Pulpcore
       - Retro about the shared remote config doc
       - Pulp does not support zero-downtime migrations.
       - 3.21 is out
### Galaxy
   - Telemetry update
   - CRC upgrade process, considering always scale down workers when there are migrations

### Open PRs
  - want to talk, link a PR to the agenda

============================================================

## August 29th
### Action Items

### Priority List
1. Collection signing (Bruno)
    * no pending items, some UI issues/improvements in progress
    * c.rh.c soon but blocked on RBAC
2. Container signing (Bruno!)
    * waiting on the RBAC branch to be merged
    * will submit a PR against master including dev env changes
3. Shared Remote Config
    * Implement on the pulp side
4. Move Ansible Namespaces to pulp ansible (higher prio)
    * there is a WIP PR in pulp-ansible for Namespace model
    * working on tests


### In the priority Queue
- PoC: Repo Management - to implement collection content type (low-medium prio)
- David's wishlist

### Pulp
   - Pulp_ansible
   - Pulp_container
   - Pulpcore
     - Is this serving the collection upload validation? https://github.com/pulp/pulpcore/pull/2963
     - will you use SystemID in pulpcore 3.20?
     - upcoming telemetry collection in 3.21
         - https://analytics.pulpproject.org/
         - See the `TELEMETRY` setting
     - Tentative pulpcore 3.21.0 release date: Sept 8th
       - https://discourse.pulpproject.org/t/pulpcore-3-21-release-schedule/573
 - general
     - FYI: PulpCon Dates: November 7-12, 2022
### Galaxy
   - Can we use pulp's import export feature to ship collections with the platform installer
       - a potential alternative https://docs.pulpproject.org/pulpcore/workflows/alternate-content-sources.html
   - OCI Env feedback?

### Open PRs
  - want to talk, link a PR to the agenda
  - Collection Version upload refactor
      - https://github.com/pulp/pulp_ansible/pull/1176

==================================================

## August 22nd

### Action Items

### Priority List
1. Collection signing (Bruno)
    * no pending items, some UI issues/improvements in progress
    * c.rh.c soon but blocked on RBAC
2. Container signing (Bruno!)
    * waiting on the RBAC branch to be merged
    * will submit a PR against master including dev env changes
3. Transition galaxy_ng to RBAC Roles (Brian M/David)
    * RBAC branch merged
    * to be tested in stage
4. Move Ansible Namespaces to pulp ansible (higher prio)
    * there is a WIP PR in pulp-ansible for Namespace model
    * working on tests


### In the priority Queue

### Pulp
   - Pulp_ansible
     - revisit renegotiate coownership
         * overall supportive
         * encourage PR reviews
     - Can we rebuild the upload workflow with Pulp facilities like SingleArtifactContentUploadViewSet, deferred_validate, ...?
       - currently pulp_ansible is reinventing all the stuff
       - https://github.com/pulp/pulp_ansible/pull/1176
       - pulp_ansible has 7 APIs for uploading collections across 5 viewsets, which can we remove? (from the generated docs):
           - `/ansible/collections/` - viewsets.CollectionUploadViewSet
           - `/pulp/api/v3/content/ansible/collection_versions/` - viewsets.CollectionVersionViewSet
           - `/pulp_ansible/galaxy/{base_path}/api/v2/collections/` - galaxy.views.GalaxyCollectionView
           - (deprecated) `/pulp_ansible/galaxy/{base_path}/api/v3/artifacts/collections/` - galaxy.v3.views.LegacyCollectionUploadViewSet
           - (deprecated) `/pulp_ansible/galaxy/default/api/v3/artifacts/collections/`  - galaxy.v3.views.LegacyCollectionUploadViewSet
           - `/pulp_ansible/galaxy/{path}/api/v3/plugin/ansible/content/{base_path}/collections/artifacts/` - galaxy.v3.views.CollectionUploadViewSet
           - `/pulp_ansible/galaxy/default/api/v3/plugin/ansible/content/{base_path}/collections/artifacts/` - galaxy.v3.views.CollectionUploadViewSet
       - We are not properly testing all these APIs in our tests
   - Pulp_container
       * https://github.com/pulp/pulp_container/issues/974 fix is merged and backported 2.8+
       * https://github.com/pulp/pulp_container/issues/977 being worked on
   - Pulpcore
       * shared remote config manager discussions continue https://github.com/pulp/pulpcore/issues/2824
### Galaxy
   - Any updates on the Namespace work?
   - Download log LGTM with (minor fixes)

### Open PRs
  - want to talk, link a PR to the agenda

==================================================

## August 15th
### Action Items
- [rtfm] discuss the state of RBAC and content isolation and distill a common goal for plugins

### Priority List
1. Collection signing (Bruno)
    * no pending items, some UI issues/improvements in progress
    * c.rh.c soon but blocked on RBAC
2. Container signing (Bruno!)
    * waiting on the RBAC branch to be merged
    * will submit a PR against master including dev env changes
3. Transition galaxy_ng to RBAC Roles (Brian M/David)
    * RBAC branch merged
    * to be tested in stage
4. Move Ansible Namespaces to pulp ansible (higher prio)
    * there is a WIP PR in pulp-ansible for Namespace model
    * working on tests

### In the priority Queue
- PoC: Repo Management - to implement collection content type (low-medium prio)
    * Architectural planning - Ina/Matthias reviewed the doc

### Pulp
   - Pulp_ansible
     * Download log
       * Will wait until tested with galaxy_ng
       * https://github.com/pulp/pulp_ansible/pull/1118
     * Moving Namespace and CollectionImport
       * https://github.com/pulp/pulp_ansible/pull/1157
   - Pulp_container

   - Pulpcore
       * https://github.com/pulp/pulpcore/issues/2952 needs review
       * Shared remote config - design discussions https://github.com/pulp/pulpcore/issues/2824
       * 
### Galaxy
   - RBAC is merged
   - Deploying collection signing to CRC planned shortly after RBAC is deployed to CRC

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls

==================================================

## August 8th
### Action Items
- [mdellweg] david, andrew, tanner, matthias, gerrod, brian? - meeting for sha256 uniqueness

### Priority List
1. Collection signing (Bruno)
    * no pending items, some UI issues/improvements in progress
3. Container signing (Bruno!)
    * waiting on the RBAC branch to be merged
    * will submit a PR against master including dev env changes
4. Transition galaxy_ng to RBAC Roles (Brian M/David)
    * almost there, hope to merge PR tomorrow
5. Move Ansible Namespaces to pulp ansible (higher prio)
    * there is a WIP PR in pulp-ansible for Namespace model

### In the priority Queue
- PoC: Repo Management - to implement collection content type (low-medium prio)
    * Architectural planning - Ina/Matthias reviewed the doc

### Pulp
   - Pulp_ansible
     * Download log
       * Will wait until tested with galaxy_ng
       * https://github.com/pulp/pulp_ansible/pull/1118
     * Sha256 digest uniqueness for CollectionVersion
       * https://github.com/pulp/pulp_ansible/pull/1119
       * We will discuss reasons with more folks next week
     * Moving Namespace and CollectionImport
       * https://github.com/pulp/pulp_ansible/pull/1157
   - Pulp_container

   - Pulpcore
       * https://github.com/pulp/pulpcore/issues/2952 PR is up, will ping AH folks for review
       * key management feature request https://github.com/pulp/pulpcore/issues/3024
       * Shared remote config 
### Galaxy
   - RBAC is worked towards merging
   - Deploying collection signing to CRC planned shortly after RBAC

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls

==================================================

## August 1st
### Action Items

### Priority List
1. Collection signing (Bruno)
2. Container signing (Bruno!)
    * waiting on the RBAC branch to be merged
4. Transition galaxy_ng to RBAC Roles (Brian M/David)
    * rebasing of the feature branch to get in sync with master
5. Logo sync / namespaces (higher prio)
    * no updates

### In the priority Queue
- PoC: Repo Management - to implement collection content type (low-medium prio)
    * Architectural planning

### Pulp
   - Pulp_ansible
     * Download log
       * Will wait until tested with galaxy_ng
       * https://github.com/pulp/pulp_ansible/pull/1118
     * Matthias is working on import export of signatures
       * https://github.com/pulp/pulp_ansible/pull/845
       * the data field needs to be converted to text field
       * This is merged
     * Sha256 digest uniqueness for CollectionVersion
       * https://github.com/pulp/pulp_ansible/pull/1119
       * We will discuss reasons with more folks next week
   - Pulp_container
       * https://github.com/pulp/pulp_container/pull/942 the fix is backported to 2.13 and will be released on Tuesday
       * schema manifest validation - great improvement upcoming https://github.com/pulp/pulp_container/pull/866
   - Pulpcore
       * https://github.com/pulp/pulpcore/issues/2952 PR is up, will ping AH folks for review
### Galaxy
   - RBAC is worked towards merging
   - Deploying collection signing to CRC planned shortly after RBAC

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls

==================================================

## July 25th
### Action Items

### Priority List
1. Collection signing (Bruno)
    * slow query issue going to be solved/tested by AH
    * https://issues.redhat.com/browse/AAP-3589 pub key management and distribution plan in place for 2.3 release
2. Container signing (Bruno!)
   * need to upgrade pulp-container to 2.11 and that needs rbac
3. Transition galaxy_ng to RBAC Roles (Brian M/David)
    * prioritizing RBAC work first
4. Logo sync / namespaces (higher prio)
    * David wrote an issue https://github.com/pulp/pulp_ansible/issues/729 @Gerrod is working on that

### In the priority Queue
- PoC: Repo Management - to implement collection content type (low-medium prio)
    * started to work on UI
    * some issues to be addressed on AH side
    * Mockups:
        * https://marvelapp.com/prototype/963i3bd/screen/87982049
        * https://marvelapp.com/prototype/963i3bd/screen/88027879

### Pulp
   - Pulp_ansible
     * Download log
       * Need feedback
       * https://github.com/pulp/pulp_ansible/pull/1118
     * Matthias is working on import export of signatures
       * https://github.com/pulp/pulp_ansible/pull/845
       * the data field needs to be converted to text field
     * Sha256 digest uniqueness for CollectionVersion
       * https://github.com/pulp/pulp_ansible/pull/1119
   - Pulp_container
      * https://github.com/pulp/pulp_container/issues/918 ok to put in the backlog for now
   - Pulpcore
       * https://github.com/pulp/pulpcore/issues/2952 PR is up: https://github.com/pulp/pulpcore/pull/2992 and it is ready for review
### Galaxy
  * mostly the focus is on RBAC

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls



==================================================
## July 18th
### Action Items

### Priority List
1. Collection signing (Bruno)
    * https://issues.redhat.com/browse/AAH-1780 verification changes
    * https://issues.redhat.com/browse/AAP-3589 pub key management and distribution
2. Container signing (Bruno!)
   * QE has a test plan
3. Transition galaxy_ng to RBAC Roles (Brian M/David)
    * Waiting for cloud deployment. Date July 26th
4. Logo sync / namespaces (higher prio)
    * Namespaces are for RBAC only 
    * Logos will be represented elsewhere
    * David wrote an issue https://github.com/pulp/pulp_ansible/issues/729

### In the priority Queue
- PoC: Repo Management - to implement collection content type (low-medium prio)
    * started to work on UI
    * some issues to be addressed on AH side
    * Mockups:
        * https://marvelapp.com/prototype/963i3bd/screen/87982049
        * https://marvelapp.com/prototype/963i3bd/screen/88027879

### Pulp
   - Pulp_ansible
     * verification changes upcoming in pulp_ansible
       * https://github.com/pulp/pulp_ansible/pull/1088 merged 
       * https://issues.redhat.com/browse/AAH-1780 
       * Matthias is working on CLI counterpart
     * Download log
       * Need feedback
       * https://github.com/pulp/pulp_ansible/pull/1118
   - Pulp_container
      * https://github.com/pulp/pulp_container/issues/918
   - Pulpcore
       * https://github.com/pulp/pulpcore/issues/2952 Lubos is working on, if you have any clarification answers leave a comment on the isuse
       * Proposal to make all tests assume they are running on the same host as Pulp
           - https://discourse.pulpproject.org/t/functional-tests-will-now-run-inside-the-container-running-pulp/498/5
           - pulp-smash eventual retirement
           - 
### Galaxy

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls



==================================================
## July 11, 2022
### Action Items
[bruno] write a jira ticket for verification changes


### Priority List
1. Collection signing (Bruno)
    * verification changes upcoming in pulp_ansible
        * https://issues.redhat.com/browse/AAH-1780
    * Signed state query is too slow
        * https://github.com/ansible/galaxy_ng/pull/1351 
2. Container signing (Bruno!)
    * onboarding to container signing podman/skopeo in progress
3. Transition galaxy_ng to RBAC Roles (Brian M/David)
    * Waiting for cloud deployment. Date TBD
4. galaxy.ansible.com replacement
    * PoC available
    * bmbouter, davidN, and jtanner
5. Logo sync / namespaces (higher prio)
    * Namespaces are for RBAC only 
    * Logos will be represented elsewhere

### In the priority Queue
- PoC: Repo Management - to implement collection content type (low-medium prio)

### Pulp
   - Pulp_ansible
     * verification changes upcoming in pulp_ansible
       * https://github.com/pulp/pulp_ansible/pull/1088
       * https://issues.redhat.com/browse/AAH-1780 
   - Pulp_container
   - Pulpcore
       - dedicate 30 mins on this call to reach an agreement on https://github.com/pulp/pulpcore/issues/2865?
           - it seems that there is no disagreement, Ina and/or David to leave a comment
           - We will focus on the filter to Distributions and anticipate that it will answer all the questions
### Galaxy
   - Unlock repos during collection import/upload https://github.com/pulp/pulp_ansible/issues/1105
   - Collection metadata repair https://github.com/pulp/pulp_ansible/issues/1106

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls



## June 27th
### Action Items

### Priority List
1. Collection signing (Bruno)
    
2. Container signing (Bruno!)
    * onboarding to container signing podman/skopeo in progress
3. Transition galaxy_ng to RBAC Roles (Brian M/David)
    * waiting on pulpcore 3.20 and plugins compat with it
    
4. galaxy.ansible.com replacement
    * PoC available
    * bmbouter, davidN, and jtanner


### In the priority Queue
- Logo sync / namespaces (higher prio)
- PoC: Repo Management - to implement collection content type (low-medium prio)


### Pulp
   - Pulp_ansible
       * 3.20 compat release pulpcore>=3.20,<3.25 is pending
       * will be 0.14.0
       * planning to add sha256 checksum to content unit
           * https://github.com/pulp/pulp_ansible/issues/1052
       * we should prioritize https://github.com/pulp/pulp_ansible/issues/709
   - Pulp_container
       * 3.20 compat release pulpcore>=3.20,<3.25 is out
   - Pulpcore
       * 3.20 is out
       * plugin_template now runs all unit and functional tests against pulp as localhost
       * new pytest fixtures for signing scripts
           * https://github.com/pulp/pulpcore/commit/db02eec77542cc3ca34b77ab96e4ad3bfdb81214
### Galaxy
- may prioritize sync streaming endpoints, rate limiting still occuring https://issues.redhat.com/browse/AAH-306
- wishlist https://hackmd.io/Gm4WNQxIRemwl75nFLUs4w

## June 13th
### Action Items

### Priority List
1. synclist removal (Andrew + Adrian)
    * deployed to c.rh.c and no longer using the curate task
2. Collection signing (Bruno)
    * deploy in progress + PR up
    * need to learn how to use rpmsign to create signatures
3. Container signing (Bruno!)
    * will start this week after LDAP work
4. Transition galaxy_ng to Roles (Brian M/David)
    * would benefit from pulp team review
        * https://github.com/ansible/galaxy_ng/pull/1279
    * proxy models perms needs to be fixed maybe
    * https://github.com/pulp/pulpcore/issues/2703
5. Private cloud storage (Matthias + Andrew)
    * Waiting on pulpcore==3.20 to release
    * Waiting on pulp_ansible compat release with pulpcore>=3.20,<3.25
6. galaxy.ansible.com replacement
    * PoC available
    * bmbouter, davidN, and jtanner


### In the priority Queue
- Logo sync / namespaces (higher prio)
- PoC: Repo Management - to implement collection content type (low-medium prio)


### Pulp
   - Pulp_ansible
       * Upcoming y-release for 3.20 compat pulpcore>=3.20,<3.25
   - Pulp_container
       * Upcoming y-release for 3.20 compat pulpcore>=3.20,<3.25
       * adding import/export for container-push repos
   - Pulpcore
       * Propose moving back the 3.20 release by a few days
           * Allow the new plugin template to be applied as the release of all plugins is prepared
       * https://github.com/pulp/pulpcore/pull/2815

### Galaxy
   - 

## June 6th

### Action Items
[fabricio] to release 0.7 and 0.10
[tanya] to schedule pulp-cli meeting

### Priority List
1. synclist removal (Andrew + Adrian)
    * deployed to c.rh.c and no longer using the curate task
    * https://github.com/pulp/pulp_ansible/pull/963
    * https://github.com/pulp/pulp_ansible/pull/975
    * needs a release AI: fabricio release 0.7 and 0.10 
2. Collection signing (Bruno)
    * deploy in progress + PR up
    * need to learn how to use rpmsign to create signatures
3. Container signing (Bruno!)
    * will start next week after LDAP work
4. Transition galaxy_ng to Roles (Brian M/David)
    * would benefit from pulp team review
        * https://github.com/ansible/galaxy_ng/pull/1279
5. Private cloud storage (Matthias + Andrew)
    * skip this week so mdellweg can confirm this is done next week

    
### In the priority Queue

- Logo sync / namespaces (higher prio)
- PoC: Repo Management - to implement collection content type (low-medium prio)
- community galaxy replacement

### Pulp
   - Pulp_ansible
   - Pulp_container
      * RBAC docs
      * uses queryset_scoping from core
   - Pulpcore
      * 3.20 on track to release on June 14th, all plugins will need to release with pulpcore>=3.20,<3.25
      * Working on simpmlifying CI
          * simplifying how we install
### Galaxy
   - update on community galaxy replacement

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls

## May 23rd
### Action Items
* [andrew] invite Tanner to next pulp galaxy mtg to give update on community galaxy replacement
* [davidn] schedule namespace meeting
* [gerrod] collaborate on bugs filed by Andrew

### Priority List
1. synclist removal (Andrew + Adrian)
     * deployed to c.rh.c and no longer using the curate task
     * https://github.com/pulp/pulp_ansible/pull/963
     * https://github.com/pulp/pulp_ansible/pull/975
3. Collection signing (Bruno)
     * waiting on API rerouting
5. API rerouting (released pulpcore 3.18) (Andrew)
     * PR up, waiting on QE. once approved can deploy to staging and ephemeral: https://github.com/ansible/galaxy_ng/pull/1247
7. Container signing (Bruno?)
     * becoming higher prioritiy
9. Transition galaxy_ng to Roles (Brian M/David)
     * final review + merge of migration PR
     * @davidN has a few PRs in pulpcore
         * https://github.com/pulp/pulpcore/pull/2748
         * https://github.com/pulp/pulpcore/pull/2728
11. Private cloud storage (Matthias + Andrew)
     * fixed some things, and will give more complete update next week


### In the priority Queue
- Logo sync / namespaces (higher prio)
- PoC: Repo Management - to implement collection content type (low-medium prio)
- community galaxy replacement

### Pulp
   - Pulp_ansible
       - waiting on changed from gerrod to release as backports
   - Pulp_container
       - no updates
   - Pulpcore
       - LTS convo ongoing

### Galaxy
- should we re-route pulp apis on all galaxy ng deployments and advertise the pulp apis under the galaxy api root?

```
GET /api/galaxy/
{
    "available_versions": {
        "v3": "v3/",
        "pulp/api/v3": "pulp/api/v3"
    },
}
```

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls

## May 16, 2022
### Action Items

### Priority List
1. synclist removal (Andrew + Adrian)
     * on schedule to deploy tomorrow
3. Collection signing (Bruno)
     * waiting on API rerooting
4. API rerouting (released pulpcore 3.18) (Andrew)
     * open PR enabling this, waiting on QE review
5. Container signing (Bruno?)
     * On the queue to work on after LDAP integration task. 
7. Transition galaxy_ng to Roles (Brian M/David)
    - Are there restrictions on prefixing roles?
    	- locked roles: yes, user def roles: no
8. Private cloud storage (Matthias + Andrew)


### In the priority Queue
- Logo sync / namespaces
- PoC: Repo Management - waiting on  PMs requirements
- community galaxy replacement


### Pulp
   - Pulp_ansible
       - need to pick an LTS branch for pulp_ansible that is compat w/ pulpcore==3.18
           - pulp-ansible 0.13.0 would align well with katello
   - Pulp_container
       * 2.1.3 is released and compat with django 2.2.28
       * 2.12.1 is released - it fixes installation dep conflicts between ansible and container plugins
   - Pulpcore
       - declaring pulpcore 3.18 as LTS
       - downloader improvements SIG underway

### Galaxy
   - Moving namespaces: https://hackmd.io/15fq1oHUS7-742SjoQBpkA
   - Question on community galaxy pulp dup key msg


### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls

==================================================

## 9th of May in the year 2022
### Action Items

### Priority List
1. synclist removal (Andrew + Adrian)
2. Collection signing (Bruno)
    * waiting for deployment 
3. API rerouting (released pulpcore 3.18) (Andrew)
    * on DEV
4. Container signing (Bruno?)
5. Transition galaxy_ng to Roles (Brian M)

### In the priority Queue
- Logo sync / namespaces
- PoC: Repo Management

### Pulp
- Pulp_ansible
  - Streaming (aka private cloud storage) brought about some challenges with galaxy-importer working on it; Coordinating with Andrew
  - Collection release date 
  	- https://issues.redhat.com/browse/AAH-1575
- Pulp_container
- Pulpcore
  - Reminder: django-guardian will be removed in 3.20
  	- example PR: https://github.com/pulp/pulp_container/commit/6e1f46f90b2fb0226b471b2f94d3a6bebd6038fb
  - merged openAPI schema tests https://github.com/pulp/pulpcore/pull/2656/files

### Galaxy
   - 

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls

==================================================

## May 2
### Action Items

### Priority List
1. Collection signing (Bruno)
2. API rerouting (released pulpcore 3.18) ( Andrew)
3. Container signing (Bruno?)
4. Transition galaxy_ng to Roles ( Brian M)
5. synclist removal ( Andrew + Adrian)
    * production issues ATM

### In the priority Queue

### Pulp
   - Pulp_ansible
   - Pulp_container
       * pulp-container 2.1 needs a release but blocked on pulpcore 3.7
   - Pulpcore
       * pulpcore 3.7 needs a backport and a release https://github.com/pulp/pulp_container/pull/745#issuecomment-1114800086
       * Streaming from private cloud storage is on track for 3.20 (including pulp_container)
           * pulp_ansible needs adjustments - https://github.com/pulp/pulp_ansible/runs/6255341995?check_suite_focus=true
       * Adding openAPI schema validator functional test (bmbouter)
           * https://github.com/pulp/pulpcore/issues/2643

### Galaxy
   - 

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls


## April 25

### Action Items

### Priority List
1. Collection signing
2. API rerouting (released pulpcore 3.18)
3. Container signing
4. Transition galaxy_ng to Roles
5. synclist removal

### In the priority Queue

### Pulp
   - Pulp_ansible
      * released 0.13
   - Pulp_container
       * prep for pulpcore 3.20 release
       * adding option to stream content through content app from object storage
       * 
   - Pulpcore
       - 3.20 will have plugin API breaking changes (not rest API)
         - remove Django-guardian
         - more deletions: Look for Deprecations
       - Discussing what the next plugin API breaking change release will be. [Current proposal](https://discourse.pulpproject.org/t/what-to-do-to-reduce-unecessary-plugin-compatibility-releases/236/15) is 3.25, so plugins can declare pulpcore>=3.20,<3.25
       - 3.19 has the swagger API that validates
           - https://docs.pulpproject.org/pulpcore/changes.html#features
### Galaxy
   - Review collection downloads: https://issues.redhat.com/browse/AAH-1537
   - Extended support for automation hub 4.2
       - pulpcore 3.7
       - pulp_ansible 0.5
       - pulp_container: N/A
   - Updating CI https://github.com/ansible/galaxy_ng/pull/1223
        * pytest for unit tests
        * CodeQL
            * https://github.com/pulp/pulp_ansible/security/code-scanning
            * https://github.com/pulp/pulp_container/security/code-scanning
            * https://discourse.pulpproject.org/t/codeql-security-analysis/438

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls

## April 18
### Action Items
- David N to look at downloader error and deterimine which team should take the next step. [DONE]
	- fixes must be rolled out on the pulp side; possibly every plugin is affected individually

### Priority List
1. Collection signing
    * working on getting signature uploads
    * some discussion of demos of this feature for summit
2. API rerouting (released pulpcore 3.18)
    * no updates, but the Pulp APIs are used for uploads so it's tied to ^
3. Container signing
    * updating to the next version of pulp_container soon
4. Transition galaxy_ng to Roles
    * may need to hold off on merging the RBAC stuff to allow the c.rh.c to be delivered on-time
    * in-progress to be kept on a feature branch

### In the priority Queue

### Pulp
   - Pulp_ansible
       - released 0.13
   - Pulp_container
   - Pulpcore
       - 3.19 was released
       - streaming binary data to users from, e.g. Azure non-routable storage feature landing in 3.20 with a new setting
       - new patch to increase logging on downloader errors
           - https://github.com/pulp/pulpcore/pull/2271
       - switched plugin_template to use pytest, when refreshing it against galaxy_ng you'll need to update a few things, please reach out on Matrix when doing so
### Galaxy
   - 

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls



## April 11
### Action Items

### Priority List
1. Collection signing
    * not a blocker: Customize the location of gpg and gpghome for gpg operations
2. API rerouting (released pulpcore 3.18)
    * next step: wait until after cloud release (12Apr) to work in stage env
3. Container signing
    * no updates
4. Transition galaxy_ng to Roles
    * removal of django-guardian is merged
    * roles translation migration is being written now


### In the priority Queue


### Pulp
   - Pulp_ansible
   - Pulp_container
       - Lubos is working on PoC/design for pull-though cache feature.
   - Pulpcore
      - pulpcore 3.19 release is scheduled for today
      - pulpcore 3.20 will contain breaking chages in plugin API
          - bmbouter doesn't think it will affect you much given the Roles transition is in-progress

### Galaxy
   - Next pulp ansible release?

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls

### Misc
* Pulp moving to pytest as test runner for functional and unittests via plugin_template
* Maintaining old branches with CI
* Should someone from the UI come here?
* When would an overview of pulp-cli be helpful?
	* What topics should we cover?

==================================================

## April 4th
### Action Items

### Priority List
1. Collection signing
    * UI work and docs
2. API rerouting ( released pulpcore 3.18)
    * next step: deploy to stage environment. Scheduled early this week
3. Container signing

### In the priority Queue
API refactor : phase 2

### Pulp
   - Pulp_ansible
     * Collection deletion needs fixes https://github.com/pulp/pulp_ansible/pull/888 (Last part of API refactor Phase I on the Pulp side, hopefully)
   - Pulp_container
     * need to document Roles https://github.com/pulp/pulp_container/issues/641
     * need to release 2.8 and 2.10
     * Lubos is wrapping up tests for syncing/pushing signatures
     * how to address missing permissions fix for existing installations https://github.com/pulp/pulp_container/pull/670
   - Pulpcore
       * the Django admin UI has been removed from 3.19

### Galaxy
- Bindings not getting generated for galaxy_ng
- 

### Open PRs
  * https://github.com/pulp/pulp_ansible/pulls
  * https://github.com/pulp/pulp_container/pulls
  * https://github.com/ansible/galaxy_ng/pulls


## March 28
### Priority list
1. Collection signing
    * UI work
    * galaxy_ng docs TBD
3. API rerouting
    * released in 3.18 
	  * next step: deploy to stage environment. No update
	  * pulp lead bmbouter
4. API refactor (phase 1 completed)
    * PR is merged ( phase 1)
    * phase 2 will start #soon, mainly work in galaxy_ng

### In the priority queue
API refactor : phase 2

### Agenda
- what happens next once we merge the plugin api refactor? phase 2 will start
- is there a JIRA for reporting the data to c.rh.c (maybe resolved in convos on slack) ( aka scheduled tasks)
    * AI: DavidN will work with the Analytics team to file a JIRA ticket


## March 14th
- installer:![](https://i.imgur.com/ESrAgXS.png)
https://issues.redhat.com/browse/AAP-1866
- Proposal: merge galaxy integraiton meeting and pulp-container meetings. Start March 28th
    * AI: Matthias extend call to 50 mins
    * AI: ipanova add container folks to this call
- Audit in galaxy_ng the code that calls .save() - it might require to dispatch a task to properly lock on resources
    * AI: Bruno will create a jira card to audit save() calls
- is there a JIRA for reporting the data to c.rh.c
    - building on this https://github.com/pulp/pulpcore/pull/2208/files#diff-b6921076eabe69f8f887286bbac04f5abb8c91b5e2e747b99ea932c5abf17135R338



## March 7th

- What's the status on the container signing integration?
    * will discuss later in another meeting

## February 14th
- [davidN] create issue for tee up the discussion regarding viewsets with customized logic in galaxy ng
    - https://github.com/pulp/pulp_ansible/issues/835
- API Spec issues
- should we release pulp_ansible with 1.0.0 with the api refactor?
    * no big -1ones

## February 7th

- what to do about viewsets with customized logic in galaxy ng?
    - Collection upload viewset
    - Collection move viewset
    - [davidN] create issue for tee up the discussion
- FYI - last piece for container signing e2e work ( sync from registry extentions API) merged
- What version of pulp ansible should the API refactor go into?
    * should be compat with pulpcore 3.18
- should we release pulp_ansible with 1.0.0 with the api refactor?
    * no big -1ones

## Jan 31

	* https://github.com/pulp/pulp_ansible/issues/773 (Download)
		* fixed in 3.15.4
	* https://github.com/pulp/pulp_ansible/issues/801 https://issues.redhat.com/browse/AAH-1243 (Proxy)
		* To be released in 0.5, 0.7 and 0.10

## Jan 24

* Next steps on getting pulp api publicly available on https://console.redhat.com/api/automation-hub/pulp/api/v3/
	* Constitute a Task Force (Members from both teams)
	* [bmbouter] showcase the api rerouting
	* [acrosby] Set up a Meeting
* AH Stage env curate task not hitting worker
	* [acrosby] Look for the tasks table and search for strangness

## Jan 17

* Bringing pulp_ansible and pulp_container together for all the things
* Issues surrounding access policies in the galaxy APIs
    * https://github.com/pulp/pulp_ansible/issues/794
* update on collection signing
* How does galaxyNG want to use the pulpcore APIs?
    * what to do about the Task API
* Check-in on creation_hooks and policy customization discussion
    * https://discourse.pulpproject.org/t/how-should-pulp-handle-different-default-permission-classes/301/6
* Migration issue https://github.com/pulp/pulp_ansible/pull/793

### Action Items
* ~~@mdellweg to invite @ipanova reocurring~~
* @davidN and @mdellweg to collaborate on it [via the issue](https://github.com/pulp/pulp_ansible/issues/794)
* ~~mdellweg to followup with @gerrod tomorrow to merge [the signing PR](https://github.com/pulp/pulp_ansible/pull/754)~~
* ~~@bmbouter to setup 30 min meeting on using (or not using) the pulp APIs, e.g. the Tasking API~~
* [Creation hooks planning](https://discourse.pulpproject.org/t/how-should-pulp-handle-different-default-permission-classes/301/6) to discuss at Jan 18th RTFM meeting with @davidN
* @fao89, @bmbouter, @mdellweg to discussion the [migraiton issue](https://github.com/pulp/pulp_ansible/pull/793) on the PR


## Jan 10

* update on collection signing
	* Branches seem to be incompatible across projects
	* Signing service setup in CI is a challenge
		* Solutions can be found in other plugins
			* https://github.com/pulp/pulp-cli/blob/main/.ci/container_setup.d/10-install-signing-service.sh
			* https://github.com/pulp/pulp_rpm/blob/main/.github/workflows/scripts/post_before_script.sh
* bug in migrations 35 and 36
    * https://github.com/pulp/pulp_ansible/issues/791
    * fix in-progress: https://github.com/pulp/pulp_ansible/pull/793
* How does galaxyNG want to use the pulpcore APIs?
	* Mainly tasking / status
	* other: Container, SigningService

## Dec 13

* OOM sync issue - https://github.com/pulp/pulp_ansible/issues/765
    * temporarily raised limits on pulp-operator
* New tasking system on consoledot - https://issues.redhat.com/browse/AAH-1150

## Dec 6
* Do you want the collection deletion APIs in pulp ansible?
	* Probably yes
* Is it possible to have a worker router for tasking system?
    * e.g: I want a task to run in a specific worker
		* Short Answer: No
		* It would not be to hard to implement, but we have some serious reservation about the implications
			* What if you request a set of capabilities that no worker provides? -> Tasking system jammed.
			* Needing a specific (type of) worker can slow down the task distribution  significantly
		* Maybe such a thing is needed, when you cannot make the single hardware crypto device available to all machines running workers

## Nov 29
* Collection Signing
	* https://github.com/pulp/pulp_ansible/pull/754
* Roles PR broke pulp_ansible CI in interesting way
* Git-sync integration continues
    * blocked on CI issues
    * https://github.com/pulp/pulp_ansible/pull/756
* Backport to release pulpcore 3.15.z
    * https://pulp.plan.io/issues/9584
* What's next for?
  * https://github.com/pulp/pulpcore/pull/1723
* API Refactor discussion on wednesday
* Writing a document describing what can be backported in the upstream
    * TL;DR any bufix without a migration. no features, no bugfixes with migrations
* Next pulpcore plugin API breaking changes will be pulpcore==3.20
    * https://pulpproject.org/2021/11/23/increasing-pulpcore-compatibility-with-plugin-versions/
* Next pulpcore release, 3.17 scheduled for Dec 6-7

## Nov 15
* Roles in pulpcore refactor
		* https://github.com/pulp/pulpcore/pull/1627
    * https://github.com/pulp/pulpcore/pull/1693
    * https://github.com/pulp/pulpcore/pull/1676
    * Can we put all the PR links here?
* Signing planning ongoing
    * meeting later today
* Git-sync integration with ansible-galaxy CLI
    * see PoC from @jtanner
        * https://github.com/ansible/galaxy_ng/pull/1042
        * https://github.com/ansible/ansible/pull/76196
        * https://github.com/ansible/ansible-hub-ui/pull/1226
        * https://github.com/ansible/galaxy-importer/pull/144
        * https://github.com/pulp/pulp_ansible/pull/672
* Sync-list implemented but on hold until more users upgrade to a pulp_ansible version that can maintain this client-side


## October 25
* As galaxy_ng is integrating more with pulp_container, we can probably arrange for meeting invites to their weekly meeting
* Synclist update

## October 18
* Azure tests
* git Remote

## October 4
* leadership transition (Matthias/Brian)
	* we may need to find a new time
		* suggestion: Mondays 16:30 CET / 10:30 ET
* ansible-lint takes more than 10 minutes on pulp_installer
    * replaced pulp.pulp_installer with pulp.squeezer to speed up tests
* Synclist tests
    * While the old synclist still active it is not possible to have functional tests

## September 27
* Planning for October
    * synclist - gerrod
    * git syncing (usage by core team in Nov)
        * bmbouter AI to find a feature lead/owner
    * download performance - psurisset has next step to retest against latest galaxyNG (pulpcore 3.14+)
        * gerrod to answer questions along the way
    * collection signing (bmbouter)
    * API refactor - David Newswanger
    * porting galaxyNG to new style RBAC Roles (gerrod/matthias?)


## September 20
* pulp_ansible leadership rotation
* proxy issue
    * 0.5.10 released
    * 0.7.4 to be released
* Synclist progress
    * Issue on galaxy side preventing syncing with v3 endpoints: https://github.com/ansible/galaxy_ng/pull/975
* Roles in pulpcore and impact on pulp_ansible and galaxyNG
    * https://discourse.pulpproject.org/t/roles-in-pulpcore/148

## September 13
* Customer issue with proxy: https://issues.redhat.com/browse/AAH-840
    * set proxy.py on pulp CI
    * maybe this fix was not backported (pulpcore 3.7, pulp_ansible 0.5) https://github.com/pulp/pulp_ansible/pull/596/files
* Import/export
    * spring? probably yes
* git stories are written
    * https://pulp.plan.io/issues/9344
    * new remote type
    * not about github, it is git!
* signing support in progress

### Actions
- @fao89: https://pulp.plan.io/issues/9390

## August 30
* Release 0.10.0
    * (X) Wait pulpcore 3.15.1
    * ( ) Apply JSONWidget fix to all JSONFields
* AH 4.4.0 check in
    * Outstanding pulp features?
* Deploy status
    * can we move forward with synclist?
* Update on Signing Support to be added (@jhardy request)
    * https://www.sigstore.dev/
* Update on initiative to replace galaxy.ansible.com's codebase while keeping role support
* Early release for Citi Bank

## August 23
* API refactor postponed
    * We're aiming to do this in 4.5 (spring release)
    * Postponded to make room for some last minute execution environment work
* CI

## August 16
* CLI tests

## August 9
* Non-blocking orphan cleanup in pulpcore 3.15
    * https://github.com/pulp/community/discussions/59
    * https://pulp.plan.io/issues/9152
    * galaxy needs update
        * make sure to touch, so the content won't be cleaned up
        * AI: [davidd] to file jira issue
* Synclist
    * AI: [fao] check with Bruno
    * candidate to move to 3.16 if can't be resolved
* 

## August 2
* Deprecation
    * only migrate latest repo version?
* Synclist
    * currently having issues to deploy galaxy
* Moving RBAC into pulp_ansible
    * AccessPolicy from DB could be an issue
    * Provide a way to make it overridable
* Content deletion
    * endpoints being implemented on galaxy_ng 
        * workflows to be implemented https://hackmd.io/e78_-T2rQRWvXaGjHT6Kyw 
    * https://pulp.plan.io/issues/7791

## July 26
* JSONField
    * defaults to jsonb
    * FROM jsonb_array_elements(cv.contents) AS cvc
    * cannot extract elements from a scalar
    * https://github.com/pulp/pulp_ansible/runs/3147479043?check_suite_focus=true#step:12:661
    * maybe PG version?
    * https://stackoverflow.com/a/39237349 
* Deprecation, ready for review
    * https://github.com/pulp/pulp_ansible/pull/593
* Max connections
    * At this moment seems more a pulpcore issue
    * https://github.com/pulp/community/discussions/55
* Deleting content
    * endpoints for deleting collection versions (DavidN work on galaxy)
* Synclist
    * currently having issues to deploy galaxy
    * only way to test right now: running locally on insights mode

## July 19
* time for 0.9.0?
    * bindings change
    * dropping support for python 3.6 and 3.7 
    * Not for now, wait for https://github.com/pulp/pulp_ansible/pull/593 and https://github.com/pulp/pulpcore/pull/1387 
* Check in on AH 4.4 work
    * https://pulp.plan.io/issues/8192 Encrypted fields
        * PR open, close to be done
        * Will land in pulpcore 3.15
    * Disk management feature(s)
        * Final feature land in pulpcore 3.15
            * https://github.com/pulp/pulpcore/pull/1452
    * https://pulp.plan.io/issues/8940 RBAC content guard
        * In progress, close to having PR open
    * High availability
        * implemented w/ 3.14, bmbouter to demo next week
    * Synclist
        * Code is ready, need to test and open PR 
    * import + export & deprecated metadata
        * https://github.com/pulp/pulp_ansible/pull/593/files
            * in-review, bmbouter next step to review
        * CLI changes
            * [david] plan to sync up with x9c4
    * configurable authorization / permission classes
        * https://pulp.plan.io/issues/8974
* Audit logging 

## July 12
* Moving to main branch
* Dropping Python 3.6/3.7 support ( := )
    * https://github.com/ansible/galaxy_ng/blob/f420c7bd774dd4908aaab4e18f72e5fa65549e5c/.travis/Containerfile.j2#L26
* Synclist /excludes/ merged, waiting deploy
    * will deploy to https://cloud.redhat.com/api/automation-hub/content/{accountnumber}-synclist/v3/excludes/
    * probably on stage/qe environment
* Import/Export is pending on CLI discussion
    * we need to make it more user friendly https://github.com/pulp/pulp-cli/issues/101
    * mdellweg/x9c4 (Matthias)
    

## June 28
* Tests are failing
    * https://pulp.plan.io/issues/8971
* Bruno requested a backport to 0.7
    * https://git.io/JnQwT
    * Not sure about timeline?

## June 21
* Add features to milestones
    * Reclaim disk space - https://pulp.plan.io/issues/8459
        * Added to pulpcore 3.15
    * Encrypted fields - https://pulp.plan.io/issues/8192
        * Added to pulpcore 3.15
    * Token auth - https://pulp.plan.io/issues/8939
        * Added to pulpcore 3.15
    * RBAC content guard - https://pulp.plan.io/issues/8940
        * Added to pulpcore 3.15
* What's the status on...
    * Import/export?
        * Meeting on Thursday with bruno
    * Content synclists?
        * Gerrod to follow up with bruno

## June 14
* What's the plan for content guards?
    * gerrod to start on writing the ticket then will
        * implement the token auth in pulpcore
        * add a content guard that is RBAC aware

## June 7

* Exclude parameter
    * currently pulp_ansible 0.7.4 has sync-task excludes filter
    * AI: bruno to implement galaxy_ng endpoint to expose synclist data
    * pulp_ansible will try to check when syncing V3 automatically, no additional user config
* Review fall deliverables with bruno and davidN

## June 3

* sprint items review
    * https://pulp.plan.io/issues?query_id=124
* review high-level deliverables through fall

## May 24

* cleaning up milestones page
    * https://pulp.plan.io/projects/ansible_plugin/roadmap
* dkliban to release 0.8
    * testing new release automation
* synclist implementation on pulp_ansible?
    * https://pulp.plan.io/issues/8194
    * @gerrod to make PoC
* freenode IRC
* Moving or not the namespace model
* What we need to go 1.0.0?
    * v4 API?
    * synclist?
    * deprecation?


## May 17
* 0.8.0
    * blocker: https://github.com/pulp/pulp_ansible/pull/563/files
    * any other blocker?
    * Will be released to be compatible with pulpcore==3.13
* Streamed endpoint
    * merged at master (future 0.8.0)
    * can be backported to 0.7 
* Synclist
    * https://pulp.plan.io/issues/8194
    * @bruno to determine where this data comes from, for now pulp_ansible will accept the `excludes` data on a remote in the same format as a requirements file
    * @gerrod will look into implementing
* Galaxy intern
* AuthN integration
* Move to github issues timeline?
    * https://github.com/omkarkhatavkar/jirasync/blob/master/jirasync/plugins/redmine.py
* FYI: fao's vacations June 7 to July 1st
    * we may need to onboard someone on installer/operator
    * probably dkliban or x9c4
* Publication
    * no issue currently written
    * next step: to review current implementation with pulp_ansible and galaxy_team together, bmbouter to schedule


## May 10
* Token auth - https://pulp.plan.io/issues/7118
    * Add to pulpcore?
* Question: which versions of pulpcore need backports for the django fix
    * https://github.com/pulp/pulpcore/pull/1306
* Query optimization - https://github.com/pulp/pulp_ansible/pull/573
* blocker for 0.8 release - https://github.com/pulp/pulp_ansible/pull/563/files
* to be done soon: https://pulp.plan.io/issues/8714


## May 5
* Testathon
    * Open invitation to test ansible automation platform 2.0
* Import/export of deprecation status
    * https://pulp.plan.io/issues/8205
    * Ansible wants import/export by AnsibleFest
    * Revisit how we handle deprecation status?
* Repo version retention
    * No global setting for now
    * Ansible will report back if they need a global setting
* Publication x streamed
    * Testing query optimization and possibly moving to publications
    * Optimizations:
        * https://github.com/pulp/pulp_ansible/pull/574
        * https://github.com/pulp/pulp_ansible/pull/573


## April 26
* Token support - https://pulp.plan.io/issues/7118
* Meetings confusion
    * pulp is currently just watcher
    * Need a place to talk about pulp_ansible features we're implementing for galaxy
* Syncing a specific version - https://pulp.plan.io/issues/8627
    * Triaged and added to sprint
    * [david] follow up with davidn and see if they need a backport
* New approach to metadata endpoint, second commit - https://github.com/pulp/pulp_ansible/pull/562
    * First: Optimize the query
    * If optimizing doesn't work, try publication
* Query optimization:
    * Collections endpoint with a complicated query: https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/galaxy/v3/views.py#L125-L263
    * CollectionVersion may get more complicated
    * Is it time to try to deduplicate?

## April 19
* Galaxy metadata
    * Publication
        * Probably still the best option
    * Streamed
        * gunicorn timeout, installer setting: https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/defaults/main.yml#L12 
            * Just set `pulp_service_timeout: 120` (or higher) on local.dev-config.yml
        * improve query performance by joining tags
        * Goal optimize the query
* https://github.com/pulp/pulpcore/pull/1204
    * Add a global setting for per repo type?
        * Leave off for now and roll it out in a future release

## April 12
* New time
    * it is ok for now
* Galaxy metadata publication - (0.9)
    * https://github.com/pulp/pulp_ansible/pull/553
    * How should I handle the published metadata requiring base_path to be created?
        * request time?
        * AI: talk with ansible-galaxy team
    *  When and who should be creating this published metadata?
        *  Galaxy: 5 repos, 5 distributions, 5 publications, ...
        *  autopublish != autodistribute https://github.com/pulp/pulp_file/pull/492#issuecomment-815378823
        *  autopublish - triggered by new repo version
        *  autodistribute - triggered by new publication?
    *  Do we want distributions to only be able to serve published content, aka remove the live update ability?
* Metadata endpoints issue (POC)
    * From unpaginated to higher pagination
    * Bring collection versions data to collections endpoint
* https://msgpack.org/index.html

## April 5
* 0.8.0 - https://pulp.plan.io/versions/186
    * dependencies sync is merged, should we release?
    * wait for token auth? synclist? ...?
* Galaxy Publication
    * pulpcore 3.12
    * needs auto-publish
* Volume testing (metadata issue) - https://hackmd.io/eXUOVP5tTPWdTOl-9uZBuQ
    * nightly performance tests? https://pulp.plan.io/issues/8478
    * pulp_file example: https://github.com/pulp/pulp_file/tree/master/pulp_file/tests/performance
* Galaxy + Pulp

## Mar 29
* synclist
    * Get alex to find out number of unused hub repos
    * Get them to delete those repos and switch back to only creating repos when opting in
    * Wait till they want to work on the feature
* repository retain versions
* tasking system
    * daniel will work with alex on this, meeting wednesday
* content removal
    * Ina is leading the resolution
    * 5 problems
        * 3 ready for working
            * https://pulp.plan.io/issues/4832
            * https://pulp.plan.io/issues/8368
            * https://pulp.plan.io/issues/7659
        * 1 @ipanova is writing up proposed solution but implementation is on-hold
        * 1 problem we are not solving
* verification trust
    * https://docs.google.com/document/d/1vmIAl2jwd3uy7UnXT4-Ev3v-_EqsoW-3KKPjnx-ouuc/edit
    * Matthias is SME, will be coming to meeting on April 12
    * Probably won't need to implement unless they really want it
    * Signatures need to syncable, potential new v3 endpoint "/signature"
* ansible execution environments?
    * Ina knows what is up
* metadata endpoint timeout bug
    * Switch to publications? Two published artifacts
        * One for "/collections/all/" 
        * One for "/collection_versions/all/"
    * They need this endpoint to work properly for their June release
    * Publication.pass_through = True
* token support - https://pulp.plan.io/issues/7118
    * https://www.django-rest-framework.org/api-guide/authentication/#tokenauthentication
    * Also needs to be verified in the content app
* update about galaxy + pulp

## Mar 22
* Move to Github Issues
* Gerrod - Commit bit
* Refinement/Grooming meetings?
* OpenAPI compliant schema?
    * https://github.com/pulp/pulpcore/pull/1122
* bmbouter is going on PPL April 5 - May 2nd
    * synclist
    * repository retain versions
    * tasking system
    * content removal
    * verification trust
* possibly combining the galaxy_ng and pulp_ansible projects?
* CI/CD
* Sync dependencies PR ready for review
    * https://github.com/pulp/pulp_ansible/pull/545

## Mar 15
* Roles support
    * https://github.com/ansible/galaxy_ng/issues/58#issuecomment-794306281
* Sync dependencies
    * https://github.com/pulp/pulp_ansible/pull/545
    * https://github.com/ansible/ansible/blob/309802214616b3981a4d2a6b3bdcf4077bd0e062/lib/ansible/galaxy/dependency_resolution/__init__.py#L31
    * may need to file other tasks:
        * dependency resolution for example
* Katello status
    * https://pulp.plan.io/issues/7118 - April? May?
    * Check with Katello at the Pulp 3 scrum on what they need and when
* Scale results
    * https://hackmd.io/eXUOVP5tTPWdTOl-9uZBuQ
    * as the repository versions grows it gets slower
* Preparing for bmbouter's leave
    * Any areas we need to onboard people?

## Mar 1st
* Foreman x Galaxy token issue - https://pulp.plan.io/issues/8290#note-4
    * Token(DRF) vs Bearer
    * Ask on Wednesday
    * Maybe 0.8.0?
* FILES.json issue - https://pulp.plan.io/issues/8292
    * Ask tomorrow
* Unpaginated serializer - https://pulp.plan.io/issues/8264
    * 0.7.1
* 0.7.1
* Ansible Contributor Summit - https://www.eventbrite.com/e/ansible-contributor-summit-202103-registration-141735886853?aff=redhat
* https://pulp.plan.io/issues/7118
    * planning to schedule a meeting with galaxy to ask about how tokens work
* Deleting & Rejecting Content

## Feb 22
* default rate_limit for AH?
    * 403 is super misleading
    * yes, maybe default for all remotes
    * what would be the default value? 10?
    * Need to document it well
    * AI: file an issue
* Satellite meeting summary?
* Check in on work
    * CI issue (nightly is breaking)
    * error when repo is empty: https://pulp.plan.io/issues/8276
    * remove unnecessary data from v3 metadata: https://pulp.plan.io/issues/8264
* galaxy.ansible.com sync failure https://pulp.plan.io/issues/8292
* Geerling and roles
    * https://galaxy.ansible.com/search?deprecated=false&keywords=geerling&order_by=-relevance&page=1
* Installer


## Feb 15
* DB denormalization - https://github.com/pulp/pulp_ansible/pull/469/files#r573247512
    * RepositoryContent.pulp_last_updated
    * Exists(AnsibleCollectionDeprecated)
    * ArrayAgg(CollectionVersion.version)
    * Collection
    * https://pulp.plan.io/issues/8262
* When can we prioritize pulp_ansible token-based content protection
    * https://pulp.plan.io/issues/7118
    * AI: discuss it during galaxy meeting
* CLI meeting with Alex
    * any AI?
    * No
* Huge JSON
    * https://github.com/ansible/galaxy_ng/pull/648#discussion_r575882363
    * waiting on jborean
* Scale testing progress
    * AWS machines setup
    * Notes: https://hackmd.io/eXUOVP5tTPWdTOl-9uZBuQ

## Feb 8th
* Retry failing tests?
    * Galaxy 520 - use rate limit feature 
    * AI: file an issue
* Import/export of collection deprecations
* Docs/CLI - Error handling: 
    * https://pulp.plan.io/issues/8216
    * Possibly bash
* Can we fix this bug:
    * https://pulp.plan.io/issues/5905
* proposal: remove tests from the redmine tracker
    * yes!
* issue: the pulp_ansible tests do not work with https://
    * CI needs to be able to run both http and https
* idea: ask galaxy_ng to release more often
* Scale testing, got the AWS machines

## Feb 1st
* python assert x unittest assertions
    * https://github.com/pulp/pulp_ansible/pull/489#discussion_r564825543
* synclists and the problems they bring
    * AI: gerrod to file a task
* katello x galaxy_ng
    * Namespace content - https://github.com/ansible/galaxy_ng/blob/master/galaxy_ng/app/models/namespace.py#L56
    * AI: ask jsherrill and Samir 


## Jan 25
* import/export
    * https://github.com/pulp/pulp_ansible/pull/503
* sync dependencies
    * https://pulp.plan.io/issues/7751
    * goal: 0.8
    * Close https://github.com/pulp/pulp_ansible/pull/398 and start a new PR
* POC: have pulp_ansible build then run ansible-lint
    * https://github.com/pulp/pulp_ansible/pull/271
    * closed

## Jan 20
* Katello
    * jsherrill is bumping the thread asking for a go/no-go on pulp_ansible supporting token auth
    * import/export work we are waiting to hear if it's needed now, but we know it will be needed so let's go ahead and work on it
* Pulpcore 3.10 ansible related things:
    * object labels [in progress] - https://github.com/pulp/pulpcore/pull/1070
    * allowing additional filtering [merged] - https://github.com/pulp/pulpcore/pull/1071
    * tasking system improvements [in review] - https://github.com/pulp/pulpcore/pull/1058
* Pulpcore 3.11?
    * https://pulp.plan.io/issues/8048
* Performance test
    * galaxy v3 collections list endpoint
* CI - Galaxy
* pulp-cli release

## Jan 11th
* Katello
    * galaxy token auth
        * possibility having tower pull ansible content from a pulp3, which is the opposite of having pulp3 pull from tower instance
        * https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#configuring-the-ansible-galaxy-client
        * https://pulp.plan.io/issues/7118
    * import/export? https://pulp.plan.io/issues/6738
        * how to handle deprecation?
    * bindings?
        * ready for testing by Katello, Pulp will fix issues as they occur
* Docs - Scripts testing
    * We only test roles - https://github.com/pulp/pulp_ansible/runs/1678977130?check_suite_focus=true
    * Should we add collections tests in this format or using pulp-cli?
    * file pulp-cli for testing collections and roles
* Content provenance
    * https://ansible.slack.com/archives/CBPKRHHG9/p1609968497314600
    * syncing a collection that is both signed and unsigned problem
        * Pulp's uniqueness constraint doesn't consider signatures so if you sync the un
    * https://pulp.plan.io/issues/8047
    * https://pulp.plan.io/issues/8049
* pulp_ansible x pulpcore
* Galaxy code owners
* How can we get Gerrod on slack?

## Jan 4th
* Onboarding Gerrod
    * performance tests
    * easy-fix bugs
    * CLI commands for pulp_ansible
* Content provenance PRD re-scheduled

## Nov 30th
* GHA
    * after nigthly runs successfully, we can try to release 0.6.0
* Status 520/403
    * Even on demand, not downloading docs-blob, concurrency = 1, couldn't sync with mitmproxy 
    * retry
        * could put all services in denial
    * how to be a good citizen for the web?
        * resume sync (download as we go)?
        * 2 remotes?
        * self-regulated rate limiting? 
            * reasonable option
            * not solve multiple syncs at same time
        * proxy?
* what do we expect from partner engineering meeting?
* what do we expect from namespace meeting?
* gerrod

## Nov 23rd
* GHA
* AH 4.3.0
    * performance testing + fixing (collections list endpoint)
        * need to set env on AWS
    * Sync namespace attributes (i.e, partner icon, links, etc.) 
        * avoid new endpoint (such as docs-blob)
        * planning
    * PE P1's
        * planning
        * AI: schedule a meeting
    * All issues are related to metadata in some degree
        * how can we make the metadata similar to pulp_rpm does?
    * Monitoring and alerting
        * gather health status?
        * k8s compatibility
* synclist
    * from server to client side


## Nov 16th
* upstream/downstream update
    * losing customers
    * shift language
* Sync 
    * #requests - https://www.redhat.com/archives/galaxy-ng/2020-November/msg00003.html
        * repository metadata?
    * refactoring status
        * we need deprecation tests
* 0.5.2
    * "everything" in POST - https://pulp.plan.io/versions/159
    * investigate https://ansible.slack.com/archives/CBPKRHHG9/p1605071034483800
    * deprecation, how to test? https://issues.redhat.com/browse/AAH-29?focusedCommentId=15430656&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-15430656
* Should we do 0.6.0 instead?
    * one issue needs migration - https://pulp.plan.io/versions/160
* More resources for pulp_ansible
* Semver - https://github.com/pulp/pulp_ansible/pull/426

## Nov 9th
* Ansible world
    * where is pulp_container used? 
        * Galaxy CLI - uses Single Container not pulp_container
        * Tower registry
* How to coordinate pulp_container x pulp_ansible with AH?
    * point to pulp_container team (Ina)
* Rewriting the sync code & tests (bmbouter in progress)
* AI: schedule pulp_ansible planning
    * Next feature release of pulp_ansible (0.6?)
    * Next week. bmbouter departs soon.



## Oct 30th
* galaxy dev env x pulplift
    * two problems:
        * galaxy_ng contributing and testing pulp_ansible is not easy
        * the installer needs to be tested continuously, i.e. with every merge
    * ask what are the barriers for using the installer
    * try to come up with a transition plan
* from Robin 
    * people need to join mini-teams being aware of what they are commiting
    * she will not assign people to the team
    * we need to slowly bring people to the team
    * AI: schedule meeting with everyone to discuss staffing (mini-team dynamic x sattelite x ansible)
* requirements.yml
    * make it compatible with galaxy cli: https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#install-multiple-collections-with-a-requirements-file
    * rewrite sync code (bmbouter)
    * bring pulp-cli to workflow docs test (daviddavis)
    * write more functional tests to cover different scenarios of requirements.yml (fao89)
* deprecation
    * CLI (jborean)
    * straightforward: DeprecationModel -> Mutable Model
* devconf.cz on-premise galaxy talk needed
    * https://docs.google.com/document/d/1Ab6CNJr7JonlHUpqp6LZTYorlEKpYI1jATktUZkKzjc/edit
    * checkin w/ daviddavis on if he's interested in presenting
    * fabricio may present, not sure yet
    * bmbouter to likely write and submit abstract, and we can swap out presenters later


## Oct 13th

* main points from galaxy meeting
    * everything points to deprecation
* mutable fields prototype
* performance issue - collections endpoint
    * PoC: https://github.com/pulp/pulp_ansible/pull/390
    * have clear definitions
    * get agreement
* django-admin
    * not merge
* AH planning x 3 months planning
    * 3mo - https://docs.google.com/spreadsheets/d/1BvelWZ9-VMatyTOPpQkMMo4A9BPGLTs6EMQzUCLenuM/edit?usp=sharing
    * AH - https://docs.google.com/spreadsheets/d/1hpTF8EjKolglxehH9Z_DiCBOa7jEwvDjolIJQ05ysh4/edit#gid=0
    * https://docs.google.com/spreadsheets/d/15jgr3UCoF7Bf7osEPD8cswV0Xs-mxUzfnVbFUTD8V8I/edit#gid=53681623
    * focus on 
        * performance evaluation and improvements
        * mutable data types
* v2 x v3 pagination issue
    * jjeffers:
Could not determine API version for: https://centos7-katello-devel-stable.example.com/pulp_ansible/galaxy/Default_Organization/Library/custom/test/test-ansible
    * any thoughts? Is there a remote config option to set the api version?
* can we make ansible contributors team?
    * read permission
    * to tag galaxy team when it is important to get their feedback
* PTO next week


## Oct 5th

* questions from @fao89
* relationship 


## Stakeholder Roundup

* ansible-galaxy CLI - maintained by ansible core team
* galaxy.ansible.com - need to be able to sync roles and collections from here
* galaxy_ng (c.rh.c)
    * need to sync collections from here
    * pulp_ansible's Galaxy V3 api is the base implementation
* katello - they use pulp_ansible
* General pulp_ansible community

## CLI integration

* role install
* collection install
* collection publish (aka upload)

## Docs
* Ansible support >= 2.6

###### tags: `Minutes`