[occi-wg] Scheduling parameters

[Ignacio Martin Llorente]

Hi,

Interesting, that is a non-functional requirement (see use case  
template at http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/UseCasesAndRequirements) 
, that for example can be embedded as part of the request. See  the  
following use case for hybrid clouds:

http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/InteroperabilityAcrossCloudInfrastructuresUsingOpenNebula

Regards
--
Ignacio M. Llorente, Full Professor (Catedratico): web http://dsa-research.org/llorente 
  and blog http://imllorente.dsa-research.org/
DSA Research Group:  web http://dsa-research.org and blog http://blog.dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org









On 14/04/2009, at 13:27, Sam Johnston wrote:

> On Tue, Apr 14, 2009 at 1:12 PM, Mehdi Sheikhalishahi <mehdi.alishahi at gmail.com 
> > wrote:
> Dear All:
>
> In the API Specification, Do you address the scheduling parameters for
> Advance Reservation, Co-allocation and others?
>
> Interesting question... I have spent a large chunk of my weekend  
> roughing up the API and rather than bundling everything in together  
> have so far opted for a core + extensions approach. This fits nicely  
> with wanting to support everything from single-user virtualised  
> desktops and hypervisors burnt into motherboards to global  
> infrastructures with millions of resources and a single entry point.
>
> For clouds (like Amazon EC2) that have fixed hardware configurations  
> rather than fluid resource allocations I'm planning to expose  
> templates. One way to implement Amazon EC2 style reservations would  
> be to implement a "reserve" actuator similar to "start", "stop" and  
> "restart". This also touches on the question of whether instances  
> persist when they are stopped - ephemeral implementations should be  
> supported as well so this is something I'm thinking about.
>
> As Andrew said, best thing for you to do is explain your  
> requirements in a use case.
>
> Sam
>
> _______________________________________________
> occi-wg mailing list
> occi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/occi-wg