> 1 and 2 -> Create an httpd::mod defined type that is a wrapper of the
> original httpd_mod, as done on https://review.openstack.org/#/c/216835/. This
> wrapper should add the before (and notify?) calls ,
> as well as skipping the call to httpd_mod in centos case
> (https://review.openstack.org
Spencer Krum writes:
> Hello All,
>
> At the meeting on August 25th, we discussed an issue with the puppet-httpd
> module and a few solutions. The issue is that the httpd_mod type does not
> have a baked-in ordering relationship with the Service['httpd'] resource.
> This means that sometimes http
So ... to summarize, we found 3 different issues:
1. Races on httpd_mod -> httpd_mod is a custom type, relying on ruby
code. It has a clear race, that is shown on all of our manifests using
that. If you use httpd_mod to install
new apache modules, they won't be applied until apache is restarted
> Do you maybe mean "after => Package['httpd']" there?
Yes. I mean 'require.'
On Thu, Aug 27, 2015 at 6:08 PM, Jeremy Stanley wrote:
> On Thu, Aug 27, 2015 at 5:38 PM, Spencer Krum
> wrote:
> [...]
> > In that case I would recommend either before => Package['httpd'] or
> before
> > => Class['ht
On Thu, Aug 27, 2015 at 5:38 PM, Spencer Krum wrote:
[...]
> In that case I would recommend either before => Package['httpd'] or before
> => Class['httpd::install']. (The second one requires us to create that
> class, but this is a pattern used by many modules to expose exactly this
> kind of hook
I went off list accidentally here. Copying in for the benefit of others.
On Thu, Aug 27, 2015 at 5:38 PM, Spencer Krum
wrote:
> In that case I would recommend either before => Package['httpd'] or before
> => Class['httpd::install']. (The second one requires us to create that
> class, but this is
On Wed, Aug 26, 2015 at 11:31:35AM -0700, Spencer Krum wrote:
> Hello All,
>
> At the meeting on August 25th, we discussed an issue with the puppet-httpd
> module and a few solutions. The issue is that the httpd_mod type does not
> have a baked-in ordering relationship with the Service['httpd'] re
On 2015-08-26 11:31:35 -0700 (-0700), Spencer Krum wrote:
[...]
> The issue is that the httpd_mod type does not have a baked-in
> ordering relationship with the Service['httpd'] resource.
[...]
This is not the only issue. We also discovered there are places
we're installing files into /etc/apache2
So... we are already consuming several modules from other providers,
relying on it. Is there some problem of trust in the puppetlabs-apache
community?
Which are the main reasons (apart from the vhost generation) that are
preventing us to rely on it, while we rely on others?
El 27/08/15 a las 2
I don't think we should plan to use puppet-apache. I think we should commit
to our fork and fix the issues we have. We can build a simple, flexible
apache module and stop. Committing to puppetlabs-apache puts us on the
roller coaster of updates and bugfixes.
The issues we are having are not hard t
I agree with that approach. We are hitting several issues with httpd_mod
that should be fixed using a defined type.
But I do believe that the way is to consume modules that are trusted by
the community, and don't put efforts on maintaining and evolving our own
modules if there are good alternati
I lean towards fixing now by using the new defined type and we write a spec
for migrating to puppetlabs-apache (once we merge in upstream infra needs).
Regards
2015-08-27 11:07 GMT+02:00 Yolanda Robla Mota :
> Hi
> Thanks for the explanation. As this is a topic that needs more background,
> and
Hi
Thanks for the explanation. As this is a topic that needs more
background, and a deeper discussion, I created an etherpad to work on it.
You can access on:
https://etherpad.openstack.org/p/puppet-httpd_vs_puppetlabs-apache
Best
Yolanda
El 26/08/15 a las 20:31, Spencer Krum escribió:
Hello
13 matches
Mail list logo
