Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite Pulp handling #218

Closed
wants to merge 6 commits into from
Closed

Rewrite Pulp handling #218

wants to merge 6 commits into from

Conversation

ekohl
Copy link
Member

@ekohl ekohl commented Nov 22, 2019

This is a WIP PR that moves all Pulp handling to a central class. It integrates the handling that puppet-katello did in the past.

This builds on a bunch of other PRs:

We can know whether we're a pulp master depending on the proxy setting.
There's no need to duplicate it.
This also includes all management that puppet-katello did in the past.
messaging_transport => 'qpid',
messaging_url => $messaging_url,
num_workers => $foreman_proxy_content::pulp_num_workers,
proxy_password => $foreman_proxy_content::pulp_proxy_password, # TODO: not in katello
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jlsherrill I recall you said Katello starts to configure Pulp 2 resources with explicit proxies rather than a server wide default. Does that mean we can drop proxy configs?

Note that previously only the Pulp 2 node had proxies configured where the Pulp 2 master had none. Does a node ever pull something from the internet? My impression was that they only mirror the Pulp 2 master.

@ehelms
Copy link
Member

ehelms commented Nov 22, 2019

It integrates the handling that puppet-katello did in the past.

Does that imply this drops the Pulp handling in puppet-katello or am I reading past the idea?

@ekohl
Copy link
Member Author

ekohl commented Nov 22, 2019

Does that imply this drops the Pulp handling in puppet-katello or am I reading past the idea?

No, that's exactly the goal. theforeman/puppet-katello#303 should reflect that side.

One huge motivator for this was also to figure out how we build vhosts. Currently the pulp vhost is used. Given we'll need to do more, I'm leaning to dropping that and explicitly defining a vhost in this module. We already have the reverse proxy on port 8443. That could actually be moved to port 443 as well (though at a later stage).

enable_puppet => $enable_puppet,
enable_rpm => $enable_yum,
manage_db => $mongodb_manage_db,
manage_httpd => $is_mirror,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume $is_mirror has value true for the proxy scenario and false for katello. Can I take the same approach when building the logic for pulp3?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is sort of based on Pulp 3 where there's no longer the concept of a master and a node. Just the is_mirror parameter. I've started to like that.

@evgeni
Copy link
Member

evgeni commented Apr 2, 2020

Ewoud says NEIN

@evgeni evgeni closed this Apr 2, 2020
@ekohl ekohl deleted the refactor-pulp branch January 14, 2021 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants