Hi Lisa,
As far as I get the main idea of your blueprint it's something that we've
planned to do in the "future". So, yes this idea is something that Blazar
should do. But the problem is that we have some real-time problems.
I mean we are in rename process (yeah, it takes real long time for us) and
our devstack job is broken (I tried to fix it, but have some problems with
time). If you want to discuss how we, I mean Blazar core-team, and you,
team from the Italian National Institute for Nuclear Physics, can
collaborate we can discuss it in irc on blazar-channel, I think. We just
need to appoint a time slot for that. May be week after summit? If I
understand you'll be there this week.



Nikolay Starodubtsev

Software Engineer

Mirantis Inc.


Skype: dark_harlequine1

2014-10-31 19:19 GMT+04:00 Lisa <lisa.zangra...@pd.infn.it>:

>  Hi Nikolay,
>
> many thanks.
> Cheers,
> Lisa
>
>
> On 31/10/2014 14:10, Nikolay Starodubtsev wrote:
>
> Hi Lisa, Sylvain,
> I'll take a look at blueprint next week and will try to left some feedback
> about it.
> Stay tuned.
>
>
>
> Nikolay Starodubtsev
>
> Software Engineer
>
> Mirantis Inc.
>
>
>  Skype: dark_harlequine1
>
> 2014-10-31 16:14 GMT+04:00 Lisa <lisa.zangra...@pd.infn.it>:
>
>>  Hi Sylvain,
>>
>> thanks for your answer.
>> Actually we haven't yet developed that because we'd like to be sure that
>> our proposal is fine with BLAZAR.
>> 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.
>> 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.
>>
>> Thanks for your attention.
>> Cheers,
>> Lisa
>>
>>
>>   Such component's name is FairShareScheduler and
>>
>>
>> On 31/10/2014 10:08, Sylvain Bauza wrote:
>>
>>
>> Le 31/10/2014 09:46, Lisa a écrit :
>>
>> Dear Sylvain and BLAZAR team,
>>
>> I'd like to receive your feedback on our blueprint (
>> https://blueprints.launchpad.net/blazar/+spec/fair-share-lease) 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?
>> Thanks in advance.
>> Cheers,
>> Lisa
>>
>>
>> Hi Lisa,
>>
>> 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.
>>
>> Thanks,
>> -Sylvain
>>
>>
>> On 28/10/2014 12:07, Lisa wrote:
>>
>> Dear Sylvain,
>>
>> as you suggested me few weeks ago, I created the blueprint (
>> https://blueprints.launchpad.net/blazar/+spec/fair-share-lease) and I'd
>> like to start a discussion.
>> 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.
>> What do you think?
>>
>> thanks in advance,
>> Cheers,
>> Lisa
>>
>>
>> On 18/09/2014 16:00, Sylvain Bauza wrote:
>>
>>
>> Le 18/09/2014 15:27, Lisa a écrit :
>>
>> Hi all,
>>
>> 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.
>> 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.
>> 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.
>> 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.
>> I would then be happy to discuss these ideas with you.
>>
>> Thanks in advance,
>> Lisa
>>
>>
>> Hi Lisa,
>>
>> Glad to see you're interested in Blazar.
>>
>> 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 ?
>> 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.
>>
>> Thanks,
>> -Sylvain
>>
>> [1] https://blueprints.launchpad.net/blazar/
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing 
>> listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing 
>> listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing 
>> listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing 
>> listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> _______________________________________________
> OpenStack-dev mailing 
> listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to