<div dir="ltr"><div>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.<br><br></div>The issues we are having are not hard to fix, imho. As with any software we build, we need to classify the problems, identify the fixes, do the work, etc.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 27, 2015 at 11:09 AM, Yolanda Robla Mota <span dir="ltr"><<a href="mailto:yolanda.robla-mota@hp.com" target="_blank">yolanda.robla-mota@hp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    I agree with that approach. We are hitting several issues with
    httpd_mod that should be fixed using a defined type.<br>
    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 alternatives. This will need a
    patch to puppetlabs-apache or a wrapper, and a proper migration
    plan, so it needs an spec.<br>
    <br>
    Best<br>
    Yolanda<br>
    <br>
    <div>El 27/08/15 a las 11:23, Ricardo
      Carrillo Cruz escribió:<br>
    </div><div><div class="h5">
    <blockquote type="cite">
      
      <div dir="ltr">I lean towards fixing now by using the new defined
        type and we write a spec
        <div>for migrating to puppetlabs-apache (once we merge in
          upstream infra needs).</div>
        <div><br>
        </div>
        <div>Regards</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">2015-08-27 11:07 GMT+02:00 Yolanda
          Robla Mota <span dir="ltr"><<a href="mailto:yolanda.robla-mota@hp.com" target="_blank">yolanda.robla-mota@hp.com</a>></span>:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div 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 href="https://etherpad.openstack.org/p/puppet-httpd_vs_puppetlabs-apache" target="_blank">https://etherpad.openstack.org/p/puppet-httpd_vs_puppetlabs-apache</a><br>
              <br>
              Best<br>
              Yolanda<br>
              <br>
              <div>El 26/08/15 a las 20:31, Spencer Krum escribió:<br>
              </div>
              <blockquote type="cite">
                <div>
                  <div>
                    <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 href="https://review.openstack.org/#/c/216708/" target="_blank">https://review.openstack.org/#/c/216708/</a><br>
                                [2] <a href="https://review.openstack.org/#/c/216436/" target="_blank">https://review.openstack.org/#/c/216436/</a><br>
                                [3] <a href="https://review.openstack.org/#/c/216835/" target="_blank">https://review.openstack.org/#/c/216835/</a><br>
                                [4] <a href="https://review.openstack.org/#/c/217334/" target="_blank">https://review.openstack.org/#/c/217334/</a><br clear="all">
                                <div>
                                  <div>
                                    <div>
                                      <div>
                                        <div><br>
                                          -- <br>
                                          <div>Spencer Krum<br>
                                            <a href="tel:%28619%29-980-7820" value="+16199807820" target="_blank">(619)-980-7820</a></div>
                                        </div>
                                      </div>
                                    </div>
                                  </div>
                                </div>
                              </div>
                            </div>
                          </div>
                        </div>
                      </div>
                    </div>
                    <br>
                    <fieldset></fieldset>
                    <br>
                  </div>
                </div>
                <pre>_______________________________________________
OpenStack-Infra mailing list
<a href="mailto:OpenStack-Infra@lists.openstack.org" target="_blank">OpenStack-Infra@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><span><font color="#888888">
</font></span></pre>
                <span><font color="#888888"> </font></span></blockquote>
              <span><font color="#888888"> <br>
                  <pre cols="72">-- 
Yolanda Robla Mota
Cloud Automation and Distribution Engineer
<a href="tel:%2B34%20605641639" value="+34605641639" target="_blank">+34 605641639</a>
<a href="mailto:yolanda.robla-mota@hp.com" target="_blank">yolanda.robla-mota@hp.com</a></pre>
                </font></span></div>
            <br>
            _______________________________________________<br>
            OpenStack-Infra mailing list<br>
            <a href="mailto:OpenStack-Infra@lists.openstack.org" target="_blank">OpenStack-Infra@lists.openstack.org</a><br>
            <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <pre cols="72">-- 
Yolanda Robla Mota
Cloud Automation and Distribution Engineer
<a href="tel:%2B34%20605641639" value="+34605641639" target="_blank">+34 605641639</a>
<a href="mailto:yolanda.robla-mota@hp.com" target="_blank">yolanda.robla-mota@hp.com</a></pre>
  </div></div></div>

<br>_______________________________________________<br>
OpenStack-Infra mailing list<br>
<a href="mailto:OpenStack-Infra@lists.openstack.org">OpenStack-Infra@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Spencer Krum<br>(619)-980-7820</div>
</div>