-
Notifications
You must be signed in to change notification settings - Fork 38
Refs #31614: Drop Pulp 2, Pulpcore only #306
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
Conversation
380bef5 to
a76c9cc
Compare
|
Here is a layout of scenarios and how they will be handled: EL8: Fresh install, no upgrade handling needed, this will install Pulpcore or Pulpcore in mirror mode EL7: New Install: Will deploy Pulpcore or Pulpcore in mirror mode along with Qpid bits to handle katello-agent Upgrade:
|
|
I tested a new install on EL7 using forklift with this PR ('checkout' merge strategy) and found that in fact Pulp 2 was still installed: Is anything else required in order to properly test? P.S. relevant configuration in forklift/roles/foreman_installer/defaults/main.yml is below: And I did validate that the changes to puppet-FPC were reflected on the provisioned box in /usr/share/foreman-installer/modules/foreman_proxy_content |
Right, of course. |
|
When I install content proxy with this PR I'm getting an AVC denial here: |
|
Installer completes successfully after |
|
puppetlabs/puppetlabs-postgresql@171a1be sould fix that btw. I'll see about nagging people for a release. |
Great, thanks. It also made me realize we need theforeman/foreman-installer#636 |
e28edc4 to
46f61f9
Compare
ekohl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like I failed to submit my review.
ekohl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should make a declaration of foreman_proxy::plugin::pulp:
class { 'foreman_proxy::plugin::pulp':
enabled => false,
pulpnode_enabled => false,
pulpcore_enabled => true,
pulpcore_mirror => $pulpcore_mirror,
pulpcore_api_url => $pulpcore_api_url, # TODO: derive this from $pulpcore::apache
pulpcore_content_url => $pulpcore_content_url, # TODO: derive this too
require => Class['pulpcore'],
}a76e64c to
aff0524
Compare
ekohl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you open an issue for this and relate the installer migration to it as well?
| $apache_https_key = $certs::apache::apache_key | ||
| $apache_https_ca = $certs::katello_default_ca_cert | ||
| $apache_https_chain = $certs::katello_server_ca_cert | ||
| if $enable_docker { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're doing a breaking change, thoughts about renaming this to $enable_container?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking a similar thing. Given this will require an installer migration alongside it, I thought to do it as an individual follow up change after this all went in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My reasoning was that it already required an installer migration anyway. Might as well combine them into one.
I now see there was one, but it wasn't in the subject. |
We can rely on the Pulpcore Apache setup now to insert the GPG fragment that proxies calls for the GPG key by repositories back to the server rather than the Pulp 2 Apache setup.
ekohl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall I think this looks good. A minor inline comment about tests. Other than that I wonder how we deal with the installed qpid. Do we clean up the installed broker or is that something we leave for other processes?
|
We still need the qpid broker for katello-agent, so we want to leave it be on upgrades. |
e6fa176 to
251cef0
Compare
ekohl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please take a look at the pub dir. It probably works, but it feels redundant.
|
Connecting the pieces, this change needs to go in alongside theforeman/foreman-installer#638 |
ekohl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small nit: probably good to require pulpcore version 3.0.0 in metadata.json for the include pulpcore fix.
This is similar in nature to #299 and #271 in it's goal. I have attempted to create individual commits that paint the picture of items that can be removed, or adjusted. The landing place for this configuration is:
This does require some ecosystem changes to go in first: