[Galaxy-ng] Galaxy/Pulp Check-in Meeting Minutes

[Chris Houseknecht]

Hey all!

Each week engineers from the Galaxy and Pulp teams meet for an hour to
discuss any issues related to the ongoing integration of Pulp Core and Pulp
Plugins into the GalaxyNG codebase <https://github.com/ansible/galaxy_ng>.
We're working together to turn the GalaxyNG project (the code that powers
Automation Hub at cloud.redhat.com) into an installable, on-premise Galaxy
capable of hosting Community, Red Hat Certified, and private Ansible
content.

The following is a summary of our last meeting, which occurred on Tuesday,
14 July:
Agenda

   - RBAC
      - need clarity on what work needs to be done and when it can be
      completed
      - adding subroute under each protected viewset named ‘access_policy’
   - Content Sync
      - more information on how remotes work and connected with
      distributions and repositories.
      - does pulp support Red Hat SSO Auth?
      - how to manage requirements.yml (Automation Hub vs Community Galaxy
      remotes).

<https://hackmd.io/GdAxjeyiT1iUpIRtvffQRg?both#Notes>Notes

   - RBAC
      - task breakdown and estimates still need to be done
      - https://github.com/rsinger86/drf-access-policy/issues/29 (discussions
      about exposing access policy via API)
      - access_policy (introspection, etc)
         - LIST - /pulp/api/v3/access_policy/
         - GET, PUT - /pulp/api/v3/access_policy/:uuid/
            - access_policy for /pulp/api/v3/remotes/file/file/
            - GET
            /pulp/api/v3/access_policy/?url=/pulp/api/v3/remotes/file/file/
         - NOTE: not suitable for checking user access
      - Content Sync
      - Pulp agreed to deliver https://pulp.plan.io/issues/7015, which
      provides ability to associate a repository with a remote.
      - Remote SSO authentication
         - implemented, but not released yet.
         - https://github.com/pulp/pulp_ansible/pull/326
         - New auth_url attribute.
      - requirements.yml options
         - hardcoding restriction in galaxy_ng, by remote name?
         - additional property, indicating if requirements.yml is required.
         - standalone remote type in addition to CollectionRemote.

<https://hackmd.io/GdAxjeyiT1iUpIRtvffQRg?both#Actions>Actions

   - [house] test https://github.com/pulp/squeezer and possibly update our
   config role to use
   - [bmbouterse] prioritize https://pulp.plan.io/issues/7015
   - [davidn] Complete RBAC task breakdown and estimates


The teams are scheduled to meet again on 21 July at 11:30 AM Eastern. You
can view the agenda and past meeting notes here
<https://hackmd.io/@galaxyng/check-in-notes>. If there is a topic you would
like us to discuss, please submit questions to the mailing list, or open an
issue at the galaxy_ng project.
<https://github.com/ansible/galaxy_ng/issues/new/choose>

Thanks!

-- 

Chris Houseknecht
Manager, Galaxy Engineering Team
Ansible by Red Hat


*GitHub: *chouseknecht
<https://www.github.com/chouseknecht>*Twitter: *@chouseknecht
<https://www.twitter.com/@chouseknecht>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/galaxy-ng/attachments/20200717/4a16b3a8/attachment.htm>