Sorry, I got the project name wrong for cloud aware scheduler … it is Synergy 
(not Symphony). The description is at 
http://indico4.twgrid.org/indico/event/1/session/22/contribution/4.pdf, also 
part of the EU Indigo Datacloud project.

Tim

On 09/06/16 07:28, "Tim Bell" <[email protected]> wrote:

>Sorry I was not able to make it. To clarify on Blazar for CERN 
>(http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-06-08-06.59.log.html),
> we’re interested in the overall problem of how to maximize the utilization of 
>the resources in the private cloud rather than a specific project at the 
>moment. 
>
>There seem to be a variety of approaches from pre-emptible VMs 
>(https://github.com/indigo-dc/opie) to a cloud aware scheduler with a queue 
>(i.e. do not return No Host Found but wait and retry) such as Symphony or some 
>of the ongoing work with HTCondor.
>
>Overall, we are trying to find a way to ensure the cloud is
>
>- Always busy by using any additional resources available for low SLA 
>activities
>- Elastic by using the low SLA resources as a buffer
>
>Blazar may be a base to build this functionality on but my current 
>understanding is that the reservations are somewhat static (i.e. reserve me X 
>instances at time Y).
>
>I’d be very interested to hear how others see this problem.
>
>Tim
>
>On 08/06/16 03:27, "Blair Bethwaite" <[email protected]> wrote:
>
>>Hi all,
>>
>>Quick reminder that the scientific-wg IRC weekly meeting is on in <6
>>hours in #openstack-meeting! Details below.
>>
>>We're planning to talk about status and use-cases for Blazar, plus
>>continued discussion/brain-storming on use-cases pertaining to our
>>focus areas. On the latter point this review from the UX team on
>>personas seems like something we should stick our oar into.
>>
>>See http://eavesdrop.openstack.org/#Scientific_Working_Group for
>>meeting details, agenda at
>>https://wiki.openstack.org/wiki/Scientific_working_group#IRC_Meeting_June_8th_2016.
>>
>>-- 
>>Cheers,
>>~Blairo
>>
>>_______________________________________________
>>User-committee mailing list
>>[email protected]
>>http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>
>_______________________________________________
>OpenStack-operators mailing list
>[email protected]
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to