<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 05/16/2018 01:02 PM, Brian Bouterse
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAAcvrTHw8PQEq+uNMjZM43W6BCTK+B6ALJb-J26Ca7C2m9UGWA@mail.gmail.com">
      <div dir="ltr">
        <div>A mini-team of @jortel, @ttereshc, @ipanova, @dkliban, and
          @bmbouter met today to discuss Lazy use-cases for Pulp3. The
          "initial" use cases would all be delivered together as the
          first implementation to be used with Pulp 3.0. The ones for
          "later" are blocked on other gaps in core's functionality
          (specifically content protection) which should come with 3.1+.<br>
        </div>
        <div><br>
        </div>
        <div>Feedback on these use cases is welcome. We are meeting
          again on this upcoming Monday, after which, we will writeup
          the work into Redmine. We'll email this thread with links to
          the Redmine plan when it's available for comment.<br>
        </div>
        <div><br>
        </div>
        <div>
          <div id="gmail-magicdomid1072" class="gmail-ace-line"><span
              class="gmail-">Initial use cases are:</span></div>
          <div id="gmail-magicdomid2327" class="gmail-ace-line">
            <ul class="gmail-list-bullet1">
              <li><span class="gmail-">pull-through caching of packages
                  (squid)</span></li>
            </ul>
          </div>
          <div id="gmail-magicdomid2328" class="gmail-ace-line">
            <ul class="gmail-list-bullet1">
              <li><span class="gmail-">parallel streaming of bits to
                  multiple clients (squid)</span></li>
            </ul>
          </div>
          <div id="gmail-magicdomid2329" class="gmail-ace-line">
            <ul class="gmail-list-bullet1">
              <li><span class="gmail-">Pulp redirects to squid when
                  content is not already downloaded (pulp)</span></li>
            </ul>
          </div>
          <div id="gmail-magicdomid2330" class="gmail-ace-line">
            <ul class="gmail-list-bullet1">
              <li><span class="gmail-">streaming data and headers
                  (streamer)</span></li>
            </ul>
          </div>
          <div id="gmail-magicdomid2360" class="gmail-ace-line">
            <ul class="gmail-list-bullet1">
              <li><span
                  class="gmail-author-a-wa5z75zjz74z6jtz69zpz72z3z68zz83zz86z">After
                  streamer downloads the content, the new Artifact is
                  created and associated with the correct </span><span
class="gmail-author-a-z77zz73zqfz66z9gz88zz70zcz88zxsalk">Content</span><span
class="gmail-author-a-wa5z75zjz74z6jtz69zpz72z3z68zz83zz86z">Artifact
                  (downloader)</span></li>
            </ul>
          </div>
          <div id="gmail-magicdomid2333" class="gmail-ace-line">
            <ul class="gmail-list-bullet1">
              <li><span class="gmail-">to use a configured downloader,
                  configured by the correct remote. This would correctly
                  configure authentication, proxy, mirrorlists, etc.
                  when fetching content (streamer)</span></li>
            </ul>
          </div>
          <div id="gmail-magicdomid826" class="gmail-ace-line"><br>
          </div>
          <div id="gmail-magicdomid1078" class="gmail-ace-line"><span
              class="gmail-">Use cases to be implemented later.
              Currently blocked because Pulp itself doesn't verify
              client entitlement for content currently.</span></div>
          <div id="gmail-magicdomid1079" class="gmail-ace-line">
            <ul class="gmail-list-bullet1">
              <li><span class="gmail-">authentication of the client to
                  verify they are entitled to the content</span></li>
            </ul>
            <div><br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Could I suggest to consider:<br>
    <br>
    * The ability to delete all downloaded content in a repository
    (basically null out the content).  I've been using this rhel7 repo
    for years, and likely all the old content is not needed anymore.  <br>
    <br>
    I've seen this requested from time to time over the past couple
    years.<br>
    <br>
    <blockquote type="cite"
cite="mid:CAAcvrTHw8PQEq+uNMjZM43W6BCTK+B6ALJb-J26Ca7C2m9UGWA@mail.gmail.com">
      <div dir="ltr">
        <div>
          <div id="gmail-magicdomid1079" class="gmail-ace-line">
            <div><br>
            </div>
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Pulp-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-dev">https://www.redhat.com/mailman/listinfo/pulp-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>