All the migrations are shipped with pulpcore[0] and will be installed when
you install pulpcore 3.15 in the new virtual env. The database has a table
that keeps track of which migrations have already been applied to it. The
installer will apply only the new migrations. Did I understand your
On Tue, Sep 21, 2021 at 4:29 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:
> Does anyone know if there is an option to only enable the content server
> in the pulp_installer? I think I could skip pulp_database and
> pulp_database_config and disable systemd api, worker, redis
Right i did not read that correctly. It's a failover scenario. It
would even be safe to flush redis on failover.
I was thinking about multiple independent content app installations
each with their own redis server. But that is another challenge.
On Tue, Sep 21, 2021 at 7:32 PM Brian Bouterse
Does anyone know if there is an option to only enable the content server in the
pulp_installer? I think I could skip pulp_database and pulp_database_config and
disable systemd api, worker, redis service once it is installed. Just wondering
if there is a better way to do this. The content only
On Mon, Sep 20, 2021 at 5:40 PM Matthias Dellweg
wrote:
> I am not sure if the cache invalidations will be pushed to all redis
> instances if deployed that way. Maybe there is a little bit of extra
> work needed.
>
I imagined the backup Pulp would have its Redis empty because that Pulp
wasn't in
