[Pulp-list] Pulp 3.15 content only server

Tue Mar 1 16:42:52 UTC 2022

Thanks, Mike. Two questions:
1) Is the advantage of manual configuration to have a independent slave redis rather than sharing the same redis?
2) Does the example configuration described in https://docs.pulpproject.org/pulp_installer/customizing/#separate-servers-for-each-and-every-service still need additional manual work that your mentioned or this example works in the latest 3.17 release? 

From: mikedep333 at redhat.com At: 02/28/22 13:52:36 UTC-5:00To:  danny.sauer at konghq.com
Cc:  Bin Li (BLOOMBERG/ 120 PARK ) ,  pulp-list at redhat.com
Subject: Re: [Pulp-list] Pulp 3.15 content only server

Hi Bin,

Using the Pulp3 Ansible Installer, we do not support a read-only server like you want. The installer could be extended to support it, as pulp 3 does support it, but we do not currently support it and overcoming #7 below would be time-consuming.

The closest you can do with the current installer (or 3.15's installer) is:
1. Run pulp_content and pulp_webserver against this server. 
2. You would configure pulp_webserver to talk only to that pulp_content instance by leaving pulp_content_bind at its default of "127.0.0.1:24816" for this host (or use a unix domain socket).
3. You'd have to point to another pulp_api server (pulp_api_bind) and redis (pulp_settings.redis_host).

Additionally, with manual configuration you can accomplish what you want:
4. Manually install & configure the redis instance to be a replica. See our pulp_redis role on how to install it and how to configure it to listen on the network: it is relatively simple to read & understand. You should actually do this before running pulp_content and pulp_webserver.
5. When running the installer against this host, pulp_settings.redis_host defaults to `localhost`, which is what you'd want instead of pointing to another pulp_redis server (contradicts #3).
6. After running the installer, manually adjust the apache/nginx config files (nginx.conf & pulp-vhost.conf) placed by pulp_webserver to not talk to any pulp-api server. pulp_webserver's  pulp_content_bind variable defaults to localhost, which makes things easier.)
7. After running the installer, manually adjust the webserver snippets from plugins (e.g., pulp_container.conf) to not talk to any API server.

See https://docs.pulpproject.org/pulp_installer/customizing/#separate-servers-for-each-and-every-service for a different example of multiple hosts, each host having a roles lists & variables.

-Mike

On Sun, Feb 27, 2022 at 4:40 PM Danny Sauer <danny.sauer at konghq.com> wrote:

You can definitely run multiple content servers as long as they all have access to the DB and files are available in the same path.

--Danny
On Sun, Feb 27, 2022, 12:23 PM Bin Li (BLOOMBERG/ 120 PARK) <bli111 at bloomberg.net> wrote:

  Just wondering if there is a documented procedure to configure additional content only server. Will it work if I only run 3 roles below and config redis as slave of the primary server? We share the external db and rsync the /var/lob/pulp/media/artifact.

  - pulp_content
  - pulp_redis
  - pulp_webserver

Thanks_______________________________________________
Pulp-list mailing list
Pulp-list at redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
 _______________________________________________
Pulp-list mailing list
Pulp-list at redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list

-- 

Mike DePaulo
He / Him / His
Service Reliability Engineer, Pulp
Red Hat
IM: mikedep333
GPG: 51745404

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20220301/ff08fd6d/attachment.htm>