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

Fixes #13451 - enables lazy sync #122

Merged
merged 1 commit into from
Feb 18, 2016
Merged

Conversation

cfouant
Copy link
Contributor

@cfouant cfouant commented Feb 4, 2016

No description provided.

@ehelms
Copy link
Member

ehelms commented Feb 5, 2016

Does Pulp turn this on by default as well?

@parthaa
Copy link
Contributor

parthaa commented Feb 9, 2016

Does Pulp turn this on by default as well?

Its off by default in pulp. We need it on for katello though.

@cfouant cfouant force-pushed the lazy-sync branch 7 times, most recently from d32779b to f388be4 Compare February 16, 2016 19:45
@cfouant cfouant changed the title [WORK IN PROGRESS]Fixes #13451 - enables lazy sync Fixes #13451 - enables lazy sync Feb 16, 2016
@cfouant cfouant force-pushed the lazy-sync branch 2 times, most recently from 684b4d2 to 56b88c3 Compare February 16, 2016 19:54
@@ -67,7 +67,7 @@
$email_from = "no-reply@${::domain}"
$email_enabled = false

$lazy_enabled = false
$lazy_enabled = true
Copy link
Member

Choose a reason for hiding this comment

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

If Pulp doesn;t enable this by default, neither should the module. This should be up to users of the module such as puppet-katello to enable.

@@ -97,4 +97,22 @@
refreshonly => true,
}
}

if $pulp::lazy_enabled {
class { '::squid3':
Copy link
Member

Choose a reason for hiding this comment

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

Is squid the Pulp supported option for lazy sync? @cristifalcas would you need a parameter here such as manage_squid or is this setup and configuration of squid if lazy sync is enabled OK?

Copy link
Contributor

Choose a reason for hiding this comment

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

its not the only supported option, any http proxy would work i would imagine, but they provide same configs for two different proxies, squid and one more that isn't in the base OS.

Copy link
Contributor

Choose a reason for hiding this comment

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

also pulp removed the lazy_enabled option from their config in the latest 2.8 nightly: pulp/pulp@0f100db

so maybe it makes more sense to just move to to a manage_squid option

@cfouant cfouant force-pushed the lazy-sync branch 2 times, most recently from 8bb6db1 to 6a5e937 Compare February 18, 2016 16:41
@@ -67,7 +67,7 @@
$email_from = "no-reply@${::domain}"
$email_enabled = false

$lazy_enabled = false
$manage_squid = true
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

If lazy is simply just "on" in Pulp now, and it requires a proxy like this squid setup to be configured then having this set to true by default is fine. I equate this to how it manages and configures mongo and apache by default.

Copy link
Contributor

Choose a reason for hiding this comment

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

Its not that its 'on' or 'off'. Its more that if you create a repo with a download policy of 'on_demand' or 'background' it requires squid to be configured and running.

I believe pulp is still using the 'immediate' policy by default which means normal pulp users not using the new feature won't need squid

Copy link
Member

Choose a reason for hiding this comment

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

Does it just continue to work as before if you use those settings but do not have squid?

Copy link
Contributor

Choose a reason for hiding this comment

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

it does, yes

Copy link
Contributor

Choose a reason for hiding this comment

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

if you use the immediate setting i mean, if you use on_demand or background, requests from clients will get a 404 i believe

Copy link
Member

Choose a reason for hiding this comment

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

Seems like a bad user experience, but whatever we can go this route and flip the bit if a user of the module comes along and wants it flipped.

Copy link
Contributor

Choose a reason for hiding this comment

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

works4me

@cfouant cfouant force-pushed the lazy-sync branch 2 times, most recently from 6c8480e to 8288860 Compare February 18, 2016 19:18
http_access => [ 'allow localhost', 'deny to_localhost', 'deny all' ],
cache => [ 'allow all' ],
maximum_object_size => '5 GB',
maximum_object_size_in_memory => '100 MB',
Copy link
Contributor

Choose a reason for hiding this comment

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

I might would make this smaller, I'm thinking somewhere closer to 1MB. I'm okay leaving this as is for now and adjusting later, but I think it needs to be tested for memory consumption at some point.

@ehelms
Copy link
Member

ehelms commented Feb 18, 2016

ACK - thanks @cfouant !

ehelms added a commit that referenced this pull request Feb 18, 2016
Fixes #13451 - enables lazy sync
@ehelms ehelms merged commit 96762b5 into theforeman:master Feb 18, 2016
cegeka-jenkins pushed a commit to cegeka/puppet-pulp that referenced this pull request Oct 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants