<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    On 05/14/15 21:04, Boris Pavlovic wrote:<br>
    <blockquote
cite="mid:CAD85om1Y1Q27Hs+mFM91u6b8=qSRH0YW8FqsRcF5_F9nQ8=-Pg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>John,</div>
        <div><br>
        </div>
        <div>I believe that backlog should be different much simpler
          then specs. </div>
        <div><br>
        </div>
        <div>Imho Operators don't have time / don't want to write long
          long specs and analyze how they are aligned with specs</div>
        <div>or moreover how they should be implemented and how they
          impact performance/security/scalability. They want </div>
        <div>just to provide feedback and someday get it
          implemented/fixed. </div>
        <div><br>
        </div>
        <div>In Rally we chose different way called "feature request". </div>
        <div>The process is the same as for specs, but template is much
          simpler. <br>
        </div>
      </div>
    </blockquote>
    Bravo!!!! <br>
    <br>
    Can we please have this as a default template and the default way to
    allow Operators to submit a feature request for EVERY and ALL the
    OpenStack projects ??<br>
    <br>
    <br>
    <blockquote
cite="mid:CAD85om1Y1Q27Hs+mFM91u6b8=qSRH0YW8FqsRcF5_F9nQ8=-Pg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>Here is the page:</div>
        <div> <a moz-do-not-send="true"
            href="https://rally.readthedocs.org/en/latest/feature_requests.html">https://rally.readthedocs.org/en/latest/feature_requests.html</a></div>
        <div><br>
        </div>
        <div>And here is the sample of feature request: </div>
        <div><a moz-do-not-send="true"
href="https://rally.readthedocs.org/en/latest/feature_request/launch_specific_benchmark.html">https://rally.readthedocs.org/en/latest/feature_request/launch_specific_benchmark.html</a></div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div>  </div>
        <div>Best regards,</div>
        <div>Boris Pavlovic </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, May 14, 2015 at 9:03 PM, Boris
          Pavlovic <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:bpavlovic@mirantis.com" target="_blank">bpavlovic@mirantis.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr">John,
              <div><br>
              </div>
              <div>I believe that backlog should be different much
                simpler then specs. </div>
              <div><br>
              </div>
              <div>Imho Operators don't have time / don't want to write
                long long specs and analyze how they are aligned with
                specs</div>
              <div>or moreover how they should be implemented and how
                they impact performance/security/scalability. They want </div>
              <div>just to provide feedback and someday get it
                implemented/fixed. </div>
              <div><br>
              </div>
              <div>In Rally we chose different way called "feature
                request". </div>
              <div>The process is the same as for specs, but template is
                much simpler. </div>
              <div><br>
              </div>
              <div>Here is the page:</div>
              <div> <a moz-do-not-send="true"
                  href="https://rally.readthedocs.org/en/latest/feature_requests.html"
                  target="_blank">https://rally.readthedocs.org/en/latest/feature_requests.html</a><br>
              </div>
              <div><br>
              </div>
              <div>And here is the sample of feature request: </div>
              <div><a moz-do-not-send="true"
href="https://rally.readthedocs.org/en/latest/feature_request/launch_specific_benchmark.html"
                  target="_blank">https://rally.readthedocs.org/en/latest/feature_request/launch_specific_benchmark.html</a></div>
              <div><br>
              </div>
              <div><br>
              </div>
              <div>  </div>
              <div>Best regards,</div>
              <div>Boris Pavlovic </div>
            </div>
            <div class="HOEnZb">
              <div class="h5">
                <div class="gmail_extra"><br>
                  <div class="gmail_quote">On Thu, May 14, 2015 at 8:47
                    PM, John Garbutt <span dir="ltr"><<a
                        moz-do-not-send="true"
                        href="mailto:john@johngarbutt.com"
                        target="_blank">john@johngarbutt.com</a>></span>
                    wrote:<br>
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
                      <br>
                      I was talking with Matt (VW) about how best some
                      large deployment<br>
                      working sessions could send their requirements to
                      Nova.<br>
                      <br>
                      As an operator, if you have a problem that needs
                      fixing or use case<br>
                      that needs addressing, a great way of raising that
                      issue with the<br>
                      developer community is a "Backlog" nova-spec.<br>
                      <br>
                      You can read more about Nova's backlog specs here:<br>
                      <a moz-do-not-send="true"
                        href="http://specs.openstack.org/openstack/nova-specs/specs/backlog/"
                        target="_blank">http://specs.openstack.org/openstack/nova-specs/specs/backlog/</a><br>
                      <br>
                      Any questions, comments or ideas, please do let me
                      know.<br>
                      <br>
                      Thanks,<br>
                      John<br>
                      <br>
                      PS<br>
                      In Kilo we formally started accepting "backlog
                      specs", although we are<br>
                      only just getting the first of these submitted
                      now. There is actually<br>
                      a patch to fix up how they get rendered:<br>
                      <a moz-do-not-send="true"
                        href="https://review.openstack.org/#/c/182793/2"
                        target="_blank">https://review.openstack.org/#/c/182793/2</a><br>
                      <br>
                      _______________________________________________<br>
                      OpenStack-operators mailing list<br>
                      <a moz-do-not-send="true"
                        href="mailto:OpenStack-operators@lists.openstack.org"
                        target="_blank">OpenStack-operators@lists.openstack.org</a><br>
                      <a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
                        target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
                    </blockquote>
                  </div>
                  <br>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-operators mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</pre>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      Best Regards,<br>
      Maish Saidel-Keesing</div>
  </body>
</html>