<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 09/18/2013 08:09 AM, Mike Asthalter
      wrote:<br>
    </div>
    <blockquote cite="mid:CE5F2637.2A5AC%25mike.asthalter@rackspace.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div>We were successful yesterday in accessing the
        orchestration-api wadl in the api-site repo from the api-ref dev
        guide (<span style="font-family: Cambria; font-size: 12px;
          color: rgb(27, 57, 245); "><span style="text-decoration:
            underline; "><a moz-do-not-send="true">https://github.com/openstack/heat/blob/master/doc/docbkx/api-ref/src/docbkx/api-ref.xml</a></span></span><span
          style="font-style: normal; font-size: 14px; text-decoration:
          none; font-weight: normal; font-family: Calibri, sans-serif; ">)
          in the original heat repo using the following syntax in the
          api-ref.xml doc:</span></div>
      <div><span style="font-style: normal; font-size: 14px;
          text-decoration: none; font-weight: normal; font-family:
          Calibri, sans-serif; "><br>
        </span></div>
      <div><span style="font-style: normal; font-size: 14px;
          text-decoration: none; font-weight: normal; font-family:
          Calibri, sans-serif; ">
          <p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px
            Helvetica; color: #b14314">
            <span style="color: #0d21a0"><wadl:resources</span><span
              style="color: #000000"><br>
            </span><span style="color: #ff9667">            href</span><span
              style="color: #ff925c">=</span><a class="moz-txt-link-rfc2396E" href="http://git.openstack.org/cgit/openstack/api-site/plain/api-ref/src/wadls/orchestration-api/src/v1/orchestration-api.wadl">"http://git.openstack.org/cgit/openstack/api-site/plain/api-ref/src/wadls/orchestration-api/src/v1/orchestration-api.wadl"</a><span
              style="color: #000000"><br>
            </span><span style="color: #ff9667">            </span><span
              style="color: #00abd2">xmlns:wadl</span><span
              style="color: #ff925c">=</span><a class="moz-txt-link-rfc2396E" href="http://wadl.dev.java.net/2009/02">"http://wadl.dev.java.net/2009/02"</a><span
              style="color: #0d21a0">/></span></p>
        </span></div>
      <div><span style="font-style: normal; font-size: 14px;
          text-decoration: none; font-weight: normal; font-family:
          Calibri, sans-serif; "><br>
        </span></div>
      <div><span style="font-style: normal; font-size: 14px;
          text-decoration: none; font-weight: normal; font-family:
          Calibri, sans-serif; ">Therefore, as recommended in our
          discussion on this mailing list last week, I am planning to
          submit a patch to delete the original heat wadl
          (heat-api-1.0.wadl) and to point the api-ref.xml doc at the
          orchestration-api.wadl in the api-site repo, as shown above. </span></div>
      <div><span style="font-style: normal; font-size: 14px;
          text-decoration: none; font-weight: normal; font-family:
          Calibri, sans-serif; "><br>
        </span></div>
      <div><span style="font-style: normal; font-size: 14px;
          text-decoration: none; font-weight: normal; font-family:
          Calibri, sans-serif; "><span class="Apple-style-span"
            style="background-color: rgb(255, 255, 0);">Please let me
            know by tomorrow if anyone has any objections to deleting
            the original heat wadl, heat-api-1.0.wadl.</span></span></div>
      <div><span style="font-style: normal; font-size: 14px;
          text-decoration: none; font-weight: normal; font-family:
          Calibri, sans-serif; "><span class="Apple-style-span"
            style="background-color: rgb(255, 255, 0);"><br>
          </span></span></div>
    </blockquote>
    There is already a change in progress to delete all of heat's
    api-ref<br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <a href="https://review.openstack.org/#/c/46412/">https://review.openstack.org/#/c/46412/</a><br>
    <br>
    <blockquote cite="mid:CE5F2637.2A5AC%25mike.asthalter@rackspace.com"
      type="cite">
      <div><span style="font-style: normal; font-size: 14px;
          text-decoration: none; font-weight: normal; font-family:
          Calibri, sans-serif; "><span class="Apple-style-span"
            style="background-color: rgb(255, 255, 0);">
          </span></span></div>
      <div>On a related note, Anne Gentle has recommended the following:</div>
      <div><br>
      </div>
      <div>"What we also need to build is logic in the build jobs so
        that any time the api-site WADL is updated, your dev guide is
        also updated. This is done in the Jenkins job in <a
          moz-do-not-send="true"
href="https://github.com/openstack-infra/config/blob/master/modules/openstack_project/files/jenkins_job_builder/config/api-jobs.yaml">https://github.com/openstack-infra/config/blob/master/modules/openstack_project/files/jenkins_job_builder/config/api-jobs.yaml</a>.
        I can either submit this patch for you, or I'll ask Steve or
        Zane to do so."</div>
      <div><br>
      </div>
      <div>Steve or Zane, is submitting this patch for the build logic
        something you would like to do, or should we ask Anne to take
        care of it?</div>
      <div><br>
      </div>
      <br>
    </blockquote>
    I would think that there is no need at all now for
    heat/doc/docbkx/api-ref since it is part of api.site. Does this mean
    there is no need for an update job?<br>
  </body>
</html>