## January 13 Agenda
* What was the previously proposed layer for the operator to take RWO
storage and convert to RWM or S3?
* [dkliban] Rook
* Need someone to join pulp-operator / galaxy_ng meeting next week
(chouseknecht's)
* fao89 is already joining.
* fao89 will be mentored by Mike on containers / k8s / operator
concepts as he makes changes
* See ["Introduction to pulp-operator"](
http://people.redhat.com/mdepaulo/presentations/Introduction%20to%20pulp-operator.pdf)
slides from pulpcon 2019
* Particularly note the ground-up explanation of layers: containers
-> k8s -> operator
* pulp-operator on github actions
* works when running at master, but fails to deploy as images are built
with podman and CI tries to push with docker -
https://github.com/pulp/pulp-operator/pull/60
* approved
* insta demo fails on PRs (failing to get remote/branch from upstream)
https://github.com/pulp/pulp-operator/pull/59/commits/0b6e5210f055731e5f64ecfb69c8e5de9861c8b2
* finish review post-meeting
* Performance issue [#8055](https://pulp.plan.io/issues/8055)
* We could selectively rework the handlers into smaller ones, and
trigger the smaller handlers, and only when needed.
* For example The task "Create configuration directory for Pulp" need
not trigger the entire big handlers "Restore SELinux contexts on Pulp dirs
that must exist"
* We could do the Pulp 2 approach: Version pulp_installer with the
SELinux policies, and run selective relabel tasks depending on what we're
upgrading to and from
* This would involve submodules or putting it in the pulp_installer
repo, ties into [#7575](https://pulp.plan.io/issues/7575)
--
Mike DePaulo
He / Him / His
Service Reliability Engineer, Pulp
Red Hat <https://www.redhat.com/>
IM: mikedep333
GPG: 51745404
<https://www.redhat.com/>
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
