[Pulp-dev] Container plugin meeting notes

[Ina Panova]

### November 23 date, 2020

AI review
* AI open a task to add OCI tests in CI--> Q1 timeframe
* AI open a PR to add pulp registry to the list of registries that
support OCI
Pulp 3:
* prioritize move from travis to gha
* rbac for repos depends on rbac for remotes. ipanova to unblock
mdellweg
* reviewed opened PRs and untriaged bugs
Pulp 2:

Open PRs:
* https://github.com/pulp/pulp_container/pulls

Un-triaged bugs:
 * https://pulp.plan.io/projects/pulp_container/issues?query_id=159

Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

AI review:

Pulp 3:
* add pulp
https://github.com/opencontainers/oci-conformance/tree/master/distribution-spec
+ enable OCI tests in CI
* AI open a task to add OCI tests in CI--> Q1
* AI open a PR to add pulp registry to the list
* https://pulp.plan.io/issues/7805 immutable tags
* https://pulp.plan.io/issues/7795 associate remote with repo
* https://pulp.plan.io/issues/7790 re-upload of artifacts

Pulp 2:

Open PRs:
* https://github.com/pulp/pulp_container/pulls

Un-triaged bugs:
 * https://pulp.plan.io/projects/pulp_container/issues?query_id=159

Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

### October 19, 2020
Pulp 3:
* Namespaces
   * proposal - merge into pulp_container repo and not wait anymore
 * let's do that
   * Matthias will look into race condition issue get_or_create()
* RBAC for repos and remotes, add on the sprint
   * https://pulp.plan.io/issues/7706
   * https://pulp.plan.io/issues/7707
* 3 months planning
   *  RBAC
   *  FIPS

Pulp 2:

Open PRs:
* https://github.com/pulp/pulp_container/pulls

Un-triaged bugs:
 * https://pulp.plan.io/projects/pulp_container/issues?query_id=159


Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

Pulp 3:
* Namespaces: design decision around namespace less distribution.
* https://github.com/pulp/pulp_container/pull/158#issuecomment-698328942
* waiting on feedback from pulp-dev list
* plan to ask jsherill for feedback
* does it make sense to make it master/detail if merging the
functionality into the pulpcore repo?
* We plan to start defining RBAC work for "everything but namespaces"
* start with repo and remote
* AI ipanova will open 2 tickets for the upcoming sprint planning
* remove authors file
* https://github.com/pulp/pulp_container/blob/master/AUTHORS
* AI ipanova will submit PR and ask Brian on legal implications in case
he is aware
* upcoming 3 months planning
* focus on RBAC

Pulp 2:

Open PRs:
* https://github.com/pulp/pulp_container/pulls

Un-triaged bugs:
 * https://pulp.plan.io/projects/pulp_container/issues?query_id=159


Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

Pulp 3:
* Namespaces https://pulp.plan.io/issues/7089
* check how podman clients work with repos without slash
* always force a namespace or allow none? Allow none.
* allow library namespace as default or not? Drop this, we won't have a
default namespace
* namespace without /
* image name 0+ / ( mongo or mongo/test)
* namespace is part of relative path of distribution
* RBAC considerations:
* namespaces can allow creation of new repos via push or deny
* users own namespace will be created on the fly if necessary
* user cannot create other namespace via push
* OCI image builder
*  should we switch to Push container repo and use push api instead of
pulp api?
https://github.com/pulp/pulp_container/blob/master/pulp_container/app/tasks/builder.py#L77
*
https://github.com/pulp/pulp_container/blob/master/pulp_container/app/tasks/builder.py#L135
*  Let's keep ad is, just add docs that would give more context on when
is the best case to use push operation and oci image builder

Pulp 2:

Open PRs:
* https://github.com/pulp/pulp_container/pulls

Un-triaged bugs:
 * https://pulp.plan.io/projects/pulp_container/issues?query_id=159



Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

Pulp 3:
* https://pulp.plan.io/issues/7419 docker notary RFE request
* accept and evaluate for future Roadmap
* Namespaces Planning https://pulp.plan.io/issues/7089
* check how podman clients work with repos without slash
* always force a namespace or allow none?
* allow "library" namespace as default or not?
* namespace will not contain /
* image name will contain 0+ /
* namespace will be part of relative path of distribution
* namespace changes might require a 3.0 pulp_container release

Pulp 2:

Open PRs:
* https://github.com/pulp/pulp_container/pulls

Un-triaged bugs:
 * https://pulp.plan.io/projects/pulp_container/issues?query_id=159



Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] container plugin meeting notes

[Ina Panova]

Pulp 3:
1. Went through pulp_docker feedback from stakeholders and some
suggestions for pulp_container
* Rollback for push repos https://pulp.plan.io/issues/7357
* As a user I can push content to a repo but make it available later
https://pulp.plan.io/issues/7286
* As a user I can hide tags from a repo when distributing content (
have not found a user story for this idea yet)
* As a user I can sync manifests from a remote registry by digest( have
not found a user story for this idea yet)
2. Discussed possible future improvements
* As a user I can mirror a subset of platforms
https://pulp.plan.io/issues/7379
* Retention policy https://pulp.plan.io/issues/7358
   We do not provide any way on how to remove content from Push
repos.
   Docker API provides DELETE on blobs/manifests endpoints.
3.  Discussions around Namespace planning. Apparently we need to decide
on what we will focus first, topic like multi-tenancy for pulp resources
also bubbled up .
Usecases:
1. As a user I can create a repository within a namespace
Example: registry_path = namespace/repo_name
2. As a user, a distribution has a namespace
3. As a user, a distribution and a repository can have the same
namespace (for pulp_container push repo usecase)


Open PRs:
* https://github.com/pulp/pulp_container/pulls

Un-triaged bugs:
 * https://pulp.plan.io/projects/pulp_container/issues?query_id=159

Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

Pulp 3:

   -

   go through the long term strategy doc for the plugin
   -

   PulpTemFile https://github.com/pulp/pulp_container/pull/133
   -

  Do we leave this out of 2.0GA? Yes (PulpTemporaryFile is not working
  as supposed: https://github.com/pulp/pulpcore/pull/844
  )
  -

  Remove from 2.0 milestone, ipanova will do
  -

  Release tomorrow!
  -

   Rename milestone RBAC to 2.1.0?
   -

  Yes, mdellweg will do
  -

   Explore the idea - Possibility to install the container registry as a
   separate micro-service
   -

  File a story
  -

   ipanova will create hackmd to move from google docs
   - OCI image builder feature is in tech preview
   -

  https://github.com/pulp/pulp_container/pull/76 - adds test for
  building container image, but failed to run on travis due to kernel
  limitations on the host
  -

  Add to 3 months planning meeting, the goal is to release without tech
  preview label




Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

Pulp 3:

   -

   2.0 GA readiness check in
   -

  Push with disabled_auth does not work .Suggestion: remove
  disabled_auth=True Push will be possible only with admin creds. For pull
  operation don’t ask for token if anonymous  is allowed
  -

 Draft: https://github.com/pulp/pulp_container/pull/135
 -

  Need to keep katello compatible - they want to manage auth on their
  own
  -

 Need to have auth disabled for both pull and push operations
 -

  AI: Matthias ask Justin more info. We cannot release 2.0 in this
  broken state. Fix before GA
  - We need to write/update docs
  -

   3 months planning estimate
   -

  RBAC
  -

  import/export


Pulp 2:

   -


Open PRs:

   -

   https://github.com/pulp/pulp_docker/pulls
   -

   https://github.com/pulp/pulp_container/pulls
   -

Triage:

   -

   Un-triaged bugs
   https://pulp.plan.io/projects/pulp_container/issues?query_id=30
   -

   https://pulp.plan.io/projects/pulp_docker/issues?query_id=30



Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

August 5 , 2020

Pulp 3:

   -

   Discussed purpose of PulpTempFile and how it works
   -

  Lubos will continue to work on adding it to pulp_container
  -

   Disable cherrypick -- needs a task?dkliban will open
   -

  https://pulp.plan.io/issues/7278 work on the upcoming sprint
  -

   Let’s review and merge https://github.com/pulp/pulp_container/pull/127 I
   doubt we will have a release of pulp_container before pulpcore release
   -

   Signed schema on conversion https://pulp.plan.io/issues/7113
   -

  Close issue
  -

  Quay is not signing anymore, ipanova asked why
  -

   As a user i can push my content to a repo but make it available later
   -

  Ipanova will open a story
  -

   One last item left to close 2.0 milestone. We want to release 2.0 GA
   once pulpcore 3.6 is available
   -

  Mdellweg will take on last item

Pulp 2:

   -


Open PRs:

   -

   https://github.com/pulp/pulp_docker/pulls
   -

   https://github.com/pulp/pulp_container/pulls
   -

Triage:

   -

   Un-triaged bugs
   https://pulp.plan.io/projects/pulp_container/issues?query_id=30
   -

   https://pulp.plan.io/projects/pulp_docker/issues?query_id=30




Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

Pulp 3:

   -

   Problematic language https://pulp.plan.io/issues/7070
   -

  On the sprint. Need to allocate time to deal with it before 2.0 GA
  -

   Merge 2.0 into master branch
   -

  Dkliban will open a PR
  -

   Need to create a 1.5 branch for future import/export work
   -

  Branch from master before 2.0 merge
  -

  Ask katello on version compatibility with pulpcore
  -

   Use chunked uploads from core https://pulp.plan.io/issues/7025
   -

  Not a straightforward change, close for now
  -

   Use PulpTempFile during upload and not shared storage
   -

  Add 2.0 milestone
  -

  Matthias will open an issue
  -

   Added new RBAC milestone https://tinyurl.com/y5ekcpw4
   -

  Start with Namespaces https://pulp.plan.io/issues/7089 - last model
  to be added
  -

  Namespaces might also be used in Ansible plugin so might eventually
  move to pulpcore


Pulp 2:

   -

   RST issue - close collab with jluza and Hao
   -

   Properly log Registry errors https://github.com/pulp/pulp_docker/pull/460
   -

  Ok to merge


Open PRs:

   -

   https://github.com/pulp/pulp_docker/pulls
   -

   https://github.com/pulp/pulp_container/pulls
   -

Triage:

   -

   Un-triaged bugs
   https://pulp.plan.io/projects/pulp_container/issues?query_id=30
   -

   https://pulp.plan.io/projects/pulp_docker/issues?query_id=30





Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

Pulp 3:

   -

   Pulpcore release 3.5 will require 2.0.0.betaX and 1.x compatibility
   releases
   -

  Dkliban and mdellweg will collaborate
  -

   RBAC - keep an eye on planning
   -

  As a start attend public meeting scheduled on Thursday
  -

   Planning next 3 months:
   -

  import /export work
  -

  RBAC work
  -

  Work for 2.0 milestone https://tinyurl.com/ya4t993x
  -

  Performance work

ipanova will come up with FTE estimation and run by the mini team


   -

   Delta containers -
   https://blogs.gnome.org/alexl/2020/05/13/putting-container-updates-on-a-diet/
   -

  https://github.com/containers/image/pull/902
  -

  ipanova open epic - as a user i can sync/push delta containers
  -

  Keep an eye on the PR, provide feedback when appropriate. Since this
  is wip this is a good time for possible collaboration.
  -

   Source containers
   - might need to get this in soonish
  -

  https://pulp.plan.io/issues/6922


Pulp 2:

   -


Open PRs:

   -

   https://github.com/pulp/pulp_docker/pulls
   -

   https://github.com/pulp/pulp_container/pulls
   -

Triage:

   -

   Un-triaged bugs
   https://pulp.plan.io/projects/pulp_container/issues?query_id=30
   -

   https://pulp.plan.io/projects/pulp_docker/issues?query_id=30
   




Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

Pulp 3:

   -

   Token auth refactor
   -

  Use of content_guard in https://pulp.plan.io/issues/6894#note-4
  -

   Make token_auth authenticateable to admin. -> open a ticket [mdellweg]
   - There will be anonymous token with pull privileges and token with
  admin(basic auth) credential with pull/push privileges
  -

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

   https://hackmd.io/kb0a-ebWTA2eLuMbnM2Qzg?view docker push issues
   -

  ContainerRepo/ContainerPushRepo types -->story [ipanova]
  -

  Add distributions validation logic -->story [dkliban]
  -

   Enable black formatting https://pulp.plan.io/issues/5302
   -

  +1, against 2.0 branch, low prio when we have a window
  -

   Close out TempRepoVersion story https://pulp.plan.io/issues/6822
   -

   Performance issue: look how we use futures, they might have performance
   impact
   -

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

   Investigate how to use chunk uploads from core→ open a task [?]


Pulp 2:

   -
   -


Open PRs:

   -

   https://github.com/pulp/pulp_docker/pulls
   -

   https://github.com/pulp/pulp_container/pulls
   -

Triage:

   -

   Un-triaged bugs
   https://pulp.plan.io/projects/pulp_container/issues?query_id=30
   -

   https://pulp.plan.io/projects/pulp_docker/issues?query_id=30



Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Container plugin meeting notes

[Ina Panova]

Pulp 3:

   -

   S3 support https://pulp.plan.io/issues/4456
   -

  Mdellweg will look into it
  -

   Docker push https://pulp.plan.io/issues/5027
   -

  Dennis will revive the PR. Next week team will look together at the PR
  -

   Import export epic https://pulp.plan.io/issues/6634
   - ipanova will set up a meeting to meet Galaxy/Tower team


Pulp 2:

   -

   Connection RST from redhat.registry.io during sync still occurs.
   -

  ipanova works with jluza on investigation


Open PRs:

   -

   https://github.com/pulp/pulp_docker/pulls
   -

   https://github.com/pulp/pulp_container/pulls
   -

Triage:

   -

   Un-triaged bugs
   https://pulp.plan.io/projects/pulp_container/issues?query_id=30
   -

   https://pulp.plan.io/projects/pulp_docker/issues?query_id=30


Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev