[Pulp-dev] pulp 2 + pulp 3 dev environment problem
daviddavis at redhat.com
Wed Jul 10 12:44:17 UTC 2019
+1 from me. Should we get this groomed and put onto the next sprint Friday?
On Wed, Jul 10, 2019 at 8:39 AM Brian Bouterse <bbouters at redhat.com> wrote:
> AIUI we have this support already, but we need to fix it up. The support
> comes from here:
> Currently though we need to fix both the apache and nginx configs to
> reverse proxy to 2 places if the first one 404s. first try the pulp API
> then the content app both on port 80. We have these stories as part of this
> epic here: https://pulp.plan.io/issues/4961 The apache one is here:
> On Wed, Jul 10, 2019 at 8:31 AM Dennis Kliban <dkliban at redhat.com> wrote:
>> I am proposing that we provide additional support for deploying with
>> httpd as the reverse proxy.
>> On Wed, Jul 10, 2019 at 8:27 AM David Davis <daviddavis at redhat.com>
>>> To clarify, are you proposing we should drop support for nginx in
>>> ansible-pulp in favor of apache? Or are you proposing we add support for
>>> httpd? I think the latter makes sense.
>>> On Tue, Jul 9, 2019 at 9:06 PM Dennis Kliban <dkliban at redhat.com> wrote:
>>>> Our ansible role for deploying Pulp 2 deploys httpd and has it bind
>>>> to ports 80 and 443. The ansible-pulp roles deploy nginx and have it
>>>> bind to port 80 also. When Pulp 2 is already installed, nginx fails to
>>>> We need to add support to ansible-pulp for deploying Pulp 3 with httpd
>>>> instead of nginx.
>>>> Does anyone have other solutions?
>>>>  https://github.com/pulp/pulp-ci/tree/master/ci/ansible/roles/pulp
>>>>  https://github.com/pulp/ansible-pulp
>>>> Pulp-dev mailing list
>>>> Pulp-dev at redhat.com
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev