May 20, 2020

   -

   Quay.io was down again <https://status.quay.io/> on 05-19
   -

      Normal docker client won’t let you use quay.io unless you specify it
      in image name.
      -

      We want to use DockerHub for reliability instead, we are upstream.
      -

   CI status check
   -

   Pulp_installer and pulp_rpm_prerequisites to have a github action to
   publish on galaxy
   -


      
https://github.com/theforeman/foreman-ansible-modules/blob/master/.github/workflows/release.yml
      -

      We have to use an individual user account’s API key though.
      <https://pulp.plan.io/issues/6458> Which one?
      -

         Use pulpbot github
         -

      Fao89 will file an issue
      -

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

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

   Unified release pipeline vision -
   https://hackmd.io/z8HZw9oyQ7-MAV6W5lse4g
   -

      Redmine epic
      -

      Dkliban will send an email on pulp-dev
      -

   Not all plugins are testing docs scripts
   -

      Worked on pulp_rpm - https://github.com/pulp/pulp_rpm/pull/1716
      -

      Started to work on pulp_ansible -
      https://github.com/pulp/pulp_ansible/pull/315
      -

   Pulp_container
   -

      Token_auth
      -

         Smash config - added token
         -

         TOKEN_AUTH_DISABLED, changed from True to False
         -

         Mdellweg - file a task to activate it in plugin_template
         -

      Problem with pulpcore imports
      -

         Fao89 - file an issue and mark as a blocker for 3.4.0 (milestone)
         -

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

   Data migration tests
   -

      Dkliban will schedule a meeting
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Reply via email to