<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi<br>
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.<br>
You can access on: <br>
<a class="moz-txt-link-freetext" href="https://etherpad.openstack.org/p/puppet-httpd_vs_puppetlabs-apache">https://etherpad.openstack.org/p/puppet-httpd_vs_puppetlabs-apache</a><br>
<br>
Best<br>
Yolanda<br>
<br>
<div class="moz-cite-prefix">El 26/08/15 a las 20:31, Spencer Krum
escribió:<br>
</div>
<blockquote
cite="mid:CADt6FWOJVmQw6BfTF4-7Ae1kwjZ8e8QbHufCXCsC1zMj41xpCg@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>Hello All,<br>
<br>
</div>
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
httpd_mod resources are instantiated after the
service attempts to come up, meaning the service
cannot start.<br>
<br>
</div>
A few solutions have been proposed:<br>
<br>
</div>
1) Modify our use of the httpd_mod resource to use
'before' everywhere. This patch [1] is an example of
doing that for puppet-gerrit, we'd have to perform
similar modifications elsewhere in our code.<br>
<br>
</div>
2) Modify the httpd module to do this automatically. This
patch [2] changes the type at the ruby layer using puppet
internal apis to add an 'autobefore' on the
Service['httpd'] resource.<br>
<br>
</div>
3) Create an httpd::mod defined type that can do this
automatically. We'd have to then change every invocation of
httpd_mod to be httpd::mod. This patch [3] is the patch to
create httpd::mod and this patch [4] shows what using it
would be like. We'd have to apply changes like [4]
everywhere in our infrastructure.<br>
<br>
</div>
4) Migrate to puppetlabs-apache. This has two forms, one(4a)
involving patching that module to support our usecase and the
other(4b) where we use the existing api.<br>
<br>
</div>
I have my own opinions about what we should be doing, but this
message is meant to explain the problem and roads available to
us, not to editorialize.<br>
<div><br>
<div>
<div>
<div>
<div>[1] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/216708/">https://review.openstack.org/#/c/216708/</a><br>
[2] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/216436/">https://review.openstack.org/#/c/216436/</a><br>
[3] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/216835/">https://review.openstack.org/#/c/216835/</a><br>
[4] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/217334/">https://review.openstack.org/#/c/217334/</a><br
clear="all">
<div>
<div>
<div>
<div>
<div><br>
-- <br>
<div class="gmail_signature">Spencer Krum<br>
(619)-980-7820</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-Infra mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-Infra@lists.openstack.org">OpenStack-Infra@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Yolanda Robla Mota
Cloud Automation and Distribution Engineer
+34 605641639
<a class="moz-txt-link-abbreviated" href="mailto:yolanda.robla-mota@hp.com">yolanda.robla-mota@hp.com</a></pre>
</body>
</html>