<div dir="ltr">Hi Lisa, Sylvain,<br>I'll take a look at blueprint next week and will try to left some feedback about it.<br>Stay tuned.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><font color="#888888"><div dir="ltr"><div style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif"><p style="font-size:small;margin:0px;font-family:Helvetica">
</p><p style="font-size:small;margin:0px;font-family:Helvetica"><b><u>                                  </u></b></p><p style="font-size:small;margin:0px;font-family:Helvetica">Nikolay Starodubtsev<br></p><p style="font-size:small;margin:0px;font-family:Helvetica">Software Engineer</p><p style="font-size:small;margin:0px;font-family:Helvetica">
Mirantis Inc.<br></p><p style="font-size:small;margin:0px;font-family:Helvetica"><br></p><p style="font-size:small;margin:0px;font-family:Helvetica">Skype: dark_harlequi<font color="#888888">ne1</font><br></p></div></div></font></div></div></div>
<br><div class="gmail_quote">2014-10-31 16:14 GMT+04:00 Lisa <span dir="ltr"><<a href="mailto:lisa.zangrando@pd.infn.it" target="_blank">lisa.zangrando@pd.infn.it</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">
    <div>Hi Sylvain,<br>
      <br>
      thanks for your answer.<br>
      Actually we haven't yet developed that because we'd like to be
      sure that our proposal is fine with BLAZAR.<br>
      We already implemented a pluggable advanced scheduler for Nova
      which addresses the issues we are experiencing with OpenStack in
      the Italian National Institute for Nuclear Physics. This scheduler
      named FairShareScheduler is able to make OpenStack more efficient
      and flexible in terms of resource usage. Of course we wish to
      integrate our work in OpenStack and so we tried several times to
      start a discussion and a possible interaction with the OpenStack
      developers, but it seems to be so difficult to do it.<br>
      The GANTT people suggested us to refer to BLAZAR because it may
      have more affinity with our scope. Is it so? Therefore, I would
      appreciate to know if you may be interested in our proposal.<br>
      <br>
      Thanks for your attention.<br>
      Cheers,<br>
      Lisa<br>
      <br>
      <br>
        Such component's name is FairShareScheduler and <br><div><div class="h5">
      <br>
      <br>
      On 31/10/2014 10:08, Sylvain Bauza wrote:<br>
    </div></div></div><div><div class="h5">
    <blockquote type="cite">
      
      <br>
      <div>Le 31/10/2014 09:46, Lisa a écrit :<br>
      </div>
      <blockquote type="cite">
        
        <div>Dear Sylvain and BLAZAR team,<br>
          <br>
          I'd like to receive your feedback on our blueprint (<a href="https://blueprints.launchpad.net/blazar/+spec/fair-share-lease" target="_blank">https://blueprints.launchpad.net/blazar/+spec/fair-share-lease</a>)
          and start a discussion in Paris the next week at the OpenStack
          Summit. Do you have a time slot for a very short meeting on
          this?<br>
          Thanks in advance.<br>
          Cheers,<br>
          Lisa<br>
          <br>
        </div>
      </blockquote>
      <br>
      Hi Lisa,<br>
      <br>
      At the moment, I'm quite occupied on Nova to split out the
      scheduler, so I can't hardly dedicate time for Blazar. That said,
      I would appreciate if you could propose some draft implementation
      attached to the blueprint, so I could glance at it and see what
      you aim to deliver.<br>
      <br>
      Thanks,<br>
      -Sylvain<br>
      <blockquote type="cite">
        <div> <br>
          On 28/10/2014 12:07, Lisa wrote:<br>
        </div>
        <blockquote type="cite">
          
          <div>Dear Sylvain,<br>
            <br>
            as you suggested me few weeks ago, I created the blueprint (<a href="https://blueprints.launchpad.net/blazar/+spec/fair-share-lease" target="_blank">https://blueprints.launchpad.net/blazar/+spec/fair-share-lease</a>)
            and I'd like to start a discussion.<br>
            I will be in Paris the next week at the OpenStack Summit, so
            it would be nice to talk with you and the BLAZAR team about
            my proposal in person.<br>
            What do you think?<br>
            <br>
            thanks in advance,<br>
            Cheers,<br>
            Lisa<br>
            <br>
            <br>
            On 18/09/2014 16:00, Sylvain Bauza wrote:<br>
          </div>
          <blockquote type="cite">
            
            <br>
            <div>Le 18/09/2014 15:27, Lisa a
              écrit :<br>
            </div>
            <blockquote type="cite">Hi all, <br>
              <br>
              my name is Lisa Zangrando and I work at the Italian
              National Institute for Nuclear Physics (INFN). In
              particular I am leading a team which is addressing the
              issue concerning the efficiency in the resource usage in
              OpenStack. <br>
              Currently OpenStack allows just a static partitioning
              model where the resource allocation to the user teams
              (i.e. the projects) can be done only by considering fixed
              quotas which cannot be exceeded even if there are unused
              resources (but) assigned to different projects. <br>
              We studied the available BLAZAR's documentation and, in
              agreement with Tim Bell (who is responsible the OpenStack
              cloud project at CERN), we think this issue could be
              addressed within your framework. <br>
              Please find attached a document that describes our use
              cases (actually we think that many other environments have
              to deal with the same problems) and how they could be
              managed in BLAZAR, by defining a new lease type (i.e.
              fairShare lease) to be considered as extension of the list
              of the already supported lease types. <br>
              I would then be happy to discuss these ideas with you. <br>
              <br>
              Thanks in advance, <br>
              Lisa <br>
              <br>
            </blockquote>
            <br>
            Hi Lisa,<br>
            <br>
            Glad to see you're interested in Blazar.<br>
            <br>
            I tried to go thru your proposal, but could you please post
            the main concepts of what you plan to add into an etherpad
            and create a blueprint [1] mapped to it so we could discuss
            on the implementation ?<br>
            Of course, don't hesitate to ping me or the blazar community
            in #openstack-blazar if you need help with the process or
            the current Blazar design.<br>
            <br>
            Thanks,<br>
            -Sylvain<br>
            <br>
            [1] <a href="https://blueprints.launchpad.net/blazar/" target="_blank">https://blueprints.launchpad.net/blazar/</a><br>
            <br>
            <blockquote type="cite"><br>
              <fieldset></fieldset>
              <br>
              <pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
            </blockquote>
            <br>
            <br>
            <fieldset></fieldset>
            <br>
            <pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
          </blockquote>
          <br>
        </blockquote>
        <br>
        <br>
        <fieldset></fieldset>
        <br>
        <pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
      </blockquote>
      <br>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </div></div></div>

<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>