Pulp

Don't forget to think about how to handle updates in this single-container case

ggainey wrote:

Don't forget to think about how to handle updates in this single-container case

I was thinking updates will be handled by migrations application, which will happen each time the container is started. It's connected to the long-living filesystem backing the database and filesystem so each time it's started it can upgrade from the files it finds then.

As mentioned on the Mailing list (correction: accidentally replied to Tania individually):

if we do pursue this, we should at least consider using something else with less duplicate code to accomplish this, like our ansible-pulp roles with ansible-bender, or adapting our existing CI's ansible-pulp molecule container w/ systemd (normally a temporary artifact.)

Also:

We have the insta-demo already for a dead simple deployment. This use case covers a simple (but less simple) deployment for people with existing small-scale container infrastructure.

We have to be concerned with postgres & rq also

We have to account for persistent data in volume mount(s). And upgrading it over time.

#5394 Separate out building the pulpcore container image from building a plugin image, and an overall strategy for building container images with different sets of plugins, is still relevant.

I believe we can close this issue