Great! I'm glad to hear that the upgrade worked for your real-world use case.
-Mike On Thu, Aug 27, 2020 at 2:10 PM Bin Li (BLOOMBERG/ 120 PARK) < [email protected]> wrote: > Thanks Mike, This works very well. It updated database without installing > a new one. > > From: [email protected] At: 08/27/20 11:01:13 > To: Bin Li (BLOOMBERG/ 120 PARK ) <[email protected]> > Cc: [email protected] > Subject: Re: [Pulp-list] pulp 3.6.1 from 3.3 > > Hi Bin, > > It sounds like you are using external postgres but included redis and > webserver, correct? > > You could do that. However, we recommend you use the following roles list > instead on 3.6. It utilizes the smaller meta role `pulp_services`: > - pulp_redis > - pulp_services > - pulp_health_check > - pulp_webserver > > `pulp_services` includes the 4 services themselves, as well as the > `pulp_database_config` role. > https://pulp-installer.readthedocs.io/en/latest/meta_roles/pulp_services/ > > - Mike > > On Wed, Aug 26, 2020 at 5:20 PM Bin Li (BLOOMBERG/ 120 PARK) < > [email protected]> wrote: > >> We are upgrading from 3.3 with an external database. In our playbook, we >> used to include individual roles with "pulp_install_db: false". The >> pulp_all_services roles seems to install a new local database. Are we >> better off listing all roles in the playbook? >> >> Thanks >> _______________________________________________ >> Pulp-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/pulp-list > > > > -- > > Mike DePaulo > > He / Him / His > > Service Reliability Engineer, Pulp > > Red Hat <https://www.redhat.com/> > > IM: mikedep333 > > GPG: 51745404 > <https://www.redhat.com/> > > > -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat <https://www.redhat.com/> IM: mikedep333 GPG: 51745404 <https://www.redhat.com/>
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
