
Dear All: In the API Specification, Do you address the scheduling parameters for Advance Reservation, Co-allocation and others? -- Best Regards, Mehdi Sheikhalishahi

Hi Mehdi - I believe that such requirements could be expressed in the form of non-functional requirements for the provisioning of VMs/resources. Perhaps if you are interested you could spec out (on the wiki [1]) a use case that expresses these needs? I don't think however it particularly useful to "embed" such needs in the OCCI interface but rather make them part of the request supplied to the interface and then allow the provider choose to deal with them or not (Postel's law ;-)) Regards, Andy [1] http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/UseCasesAndRe... -----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of Mehdi Sheikhalishahi Sent: 14 April 2009 12:13 To: occi-wg@ogf.org Subject: [occi-wg] Scheduling parameters Dear All: In the API Specification, Do you address the scheduling parameters for Advance Reservation, Co-allocation and others? -- Best Regards, Mehdi Sheikhalishahi _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

This is something that could be also interesting for the Grid Scheduling Architecture Research Group (GSA-RG) within OGF. You might want to cc: their (our ;-) ) list as well when discussing scheduling- related issues. We are currently discussing the notion of delegating activities (jobs, basically) and resources between management instances (schedulers so far). The latter might also be something that tackles OCCI. -Alexander Am 14.04.2009 um 13:19 schrieb Edmonds, AndrewX:
Hi Mehdi - I believe that such requirements could be expressed in the form of non-functional requirements for the provisioning of VMs/ resources. Perhaps if you are interested you could spec out (on the wiki [1]) a use case that expresses these needs? I don't think however it particularly useful to "embed" such needs in the OCCI interface but rather make them part of the request supplied to the interface and then allow the provider choose to deal with them or not (Postel's law ;-))
Regards,
Andy
[1] http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/UseCasesAndRe...
-----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of Mehdi Sheikhalishahi Sent: 14 April 2009 12:13 To: occi-wg@ogf.org Subject: [occi-wg] Scheduling parameters
Dear All:
In the API Specification, Do you address the scheduling parameters for Advance Reservation, Co-allocation and others?
-- Best Regards, Mehdi Sheikhalishahi _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
-- Alexander Papaspyrou alexander.papaspyrou@tu-dortmund.de

+1 As a general rule please can we make sure we DO contact other groups in OGF and beyond, so that we don't replicate their work, and so that they can provide use cases for OCCI. alexis On Tue, Apr 14, 2009 at 2:19 PM, Alexander Papaspyrou <alexander.papaspyrou@tu-dortmund.de> wrote:
This is something that could be also interesting for the Grid Scheduling Architecture Research Group (GSA-RG) within OGF. You might want to cc: their (our ;-) ) list as well when discussing scheduling-related issues.
We are currently discussing the notion of delegating activities (jobs, basically) and resources between management instances (schedulers so far). The latter might also be something that tackles OCCI.
-Alexander
Am 14.04.2009 um 13:19 schrieb Edmonds, AndrewX:
Hi Mehdi - I believe that such requirements could be expressed in the form of non-functional requirements for the provisioning of VMs/resources. Perhaps if you are interested you could spec out (on the wiki [1]) a use case that expresses these needs? I don't think however it particularly useful to "embed" such needs in the OCCI interface but rather make them part of the request supplied to the interface and then allow the provider choose to deal with them or not (Postel's law ;-))
Regards,
Andy
[1] http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/UseCasesAndRe...
-----Original Message----- From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf Of Mehdi Sheikhalishahi Sent: 14 April 2009 12:13 To: occi-wg@ogf.org Subject: [occi-wg] Scheduling parameters
Dear All:
In the API Specification, Do you address the scheduling parameters for Advance Reservation, Co-allocation and others?
-- Best Regards, Mehdi Sheikhalishahi _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
-- Alexander Papaspyrou alexander.papaspyrou@tu-dortmund.de
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

On Tue, Apr 14, 2009 at 1:12 PM, Mehdi Sheikhalishahi < mehdi.alishahi@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<http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/APIDesign>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

Can someone detail how I can add content to the wiki? Do permissions need to be assigned? I’ve an account created (AndyEdmonds). Andy Andy Edmonds skype: andy.edmonds tel: +353 (0)1 6069232 IT Research - IT Innovation Centre - Intel Ireland Ltd. Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

"All Projects" tab in the Projects option of your "My Workspace" menu. 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:43, Edmonds, AndrewX wrote:
Can someone detail how I can add content to the wiki? Do permissions need to be assigned? I’ve an account created (AndyEdmonds).
Andy
Andy Edmonds skype: andy.edmonds tel: +353 (0)1 6069232
IT Research - IT Innovation Centre - Intel Ireland Ltd. Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

Hi Andy, I just added you to the project. User must be registered to the project prior to be able to edit sth. in the wiki. Cheers, -Thijs On Tue, 2009-04-14 at 12:43 +0100, Edmonds, AndrewX wrote:
AndyEdmonds -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds Software Engineer Grid Computing Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

Thanks Thijs - odd I had registered. I guess new registrants are only assigned "Member" roles that do not have edit capabilities - would that be correct? -----Original Message----- From: Thijs.Metsch@Sun.COM [mailto:Thijs.Metsch@Sun.COM] Sent: 14 April 2009 12:58 To: Edmonds, AndrewX Cc: occi-wg@ogf.org Subject: Re: [occi-wg] Editing Wiki Hi Andy, I just added you to the project. User must be registered to the project prior to be able to edit sth. in the wiki. Cheers, -Thijs On Tue, 2009-04-14 at 12:43 +0100, Edmonds, AndrewX wrote:
AndyEdmonds -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds Software Engineer Grid Computing Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com
------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

Hi, New registrants are only added to the forge not to particular projects at all. We as the chairs have to add the persons to the projects. Either on request or invitation base. -Thijs On Tue, 2009-04-14 at 13:00 +0100, Edmonds, AndrewX wrote:
Thanks Thijs - odd I had registered. I guess new registrants are only assigned "Member" roles that do not have edit capabilities - would that be correct?
-----Original Message----- From: Thijs.Metsch@Sun.COM [mailto:Thijs.Metsch@Sun.COM] Sent: 14 April 2009 12:58 To: Edmonds, AndrewX Cc: occi-wg@ogf.org Subject: Re: [occi-wg] Editing Wiki
Hi Andy,
I just added you to the project. User must be registered to the project prior to be able to edit sth. in the wiki.
Cheers,
-Thijs
On Tue, 2009-04-14 at 12:43 +0100, Edmonds, AndrewX wrote:
AndyEdmonds -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds Software Engineer Grid Computing Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com
------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds Software Engineer Grid Computing Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

I know that other members have modified the wiki, 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 14:00, Edmonds, AndrewX wrote:
Thanks Thijs - odd I had registered. I guess new registrants are only assigned "Member" roles that do not have edit capabilities - would that be correct?
-----Original Message----- From: Thijs.Metsch@Sun.COM [mailto:Thijs.Metsch@Sun.COM] Sent: 14 April 2009 12:58 To: Edmonds, AndrewX Cc: occi-wg@ogf.org Subject: Re: [occi-wg] Editing Wiki
Hi Andy,
I just added you to the project. User must be registered to the project prior to be able to edit sth. in the wiki.
Cheers,
-Thijs
On Tue, 2009-04-14 at 12:43 +0100, Edmonds, AndrewX wrote:
AndyEdmonds -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds Software Engineer Grid Computing Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com
------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

After logging into GridForge, the occi-wg project home (http://forge.ogf.org/sf/projects/occi-wg) page should have a link 'Join this project' on the top of the left 'Project Home' panel. That leads to 'http://forge.ogf.org/sf/sfmain/do/joinProject/projects.occi-wg', which leads to a submit form to alert the group admins to your request. Once they grant you access, you can edit the wiki. Hope that helps, Andre. Quoting [Edmonds, AndrewX] (Apr 14 2009):
From: "Edmonds, AndrewX" <andrewx.edmonds@intel.com> To: "occi-wg@ogf.org" <occi-wg@ogf.org> Date: Tue, 14 Apr 2009 12:43:35 +0100 Subject: [occi-wg] Editing Wiki
Can someone detail how I can add content to the wiki? Do permissions need to be assigned? Iâve an account created (AndyEdmonds).
Andy
Andy Edmonds skype: andy.edmonds tel: +353 (0)1 6069232
IT Research - IT Innovation Centre - Intel Ireland Ltd. Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
-- Nothing is ever easy.

I added a page detailing these steps for noobs to gridforge (like me :-)) http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/ContributingT... Andy -----Original Message----- From: Andre Merzky [mailto:andremerzky@gmail.com] On Behalf Of Andre Merzky Sent: 14 April 2009 13:13 To: Edmonds, AndrewX Cc: occi-wg@ogf.org Subject: Re: [occi-wg] Editing Wiki After logging into GridForge, the occi-wg project home (http://forge.ogf.org/sf/projects/occi-wg) page should have a link 'Join this project' on the top of the left 'Project Home' panel. That leads to 'http://forge.ogf.org/sf/sfmain/do/joinProject/projects.occi-wg', which leads to a submit form to alert the group admins to your request. Once they grant you access, you can edit the wiki. Hope that helps, Andre. Quoting [Edmonds, AndrewX] (Apr 14 2009):
From: "Edmonds, AndrewX" <andrewx.edmonds@intel.com> To: "occi-wg@ogf.org" <occi-wg@ogf.org> Date: Tue, 14 Apr 2009 12:43:35 +0100 Subject: [occi-wg] Editing Wiki
Can someone detail how I can add content to the wiki? Do permissions need to be assigned? I’ve an account created (AndyEdmonds).
Andy
Andy Edmonds skype: andy.edmonds tel: +353 (0)1 6069232
IT Research - IT Innovation Centre - Intel Ireland Ltd. Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
-- Nothing is ever easy. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

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/UseCasesAndRe...) , 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/Interoperabil... 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@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@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

Quoting [Sam Johnston] (Apr 14 2009):
I have spent a large chunk of my weekend [2] roughing up the API and rather than bundling everything in together have so far opted for a core + extensions approach. ... [2] http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/APIDesign
Minor comments: - I like the extension approach - do you intent to hook GLUE into the <Info> part in your XML example, or into similar places in the API? Optionally at least? <Info>4Gb, 2 CPU, 1 disk, 2 nic virtual machine</Info> - why the purl.org/occi namespace? OGF has an established namespace for XML schemata, see http://schemas.ogf.org/, and GFD.84 on http://www.ogf.org/docs/?cp A question about the machine control extension: I am not overly familiar with the capabilities offerred by the various discussed backends, but is a 'CLONE' operation something which is being considered? That would be basically a CREATE op which refers to a running instance instead of reffering to an image and instance description (or whatever your CREATE needs as input). How would that map to your state machine? As suspend/resume (for the time a snapshot is taken)? Similar for 'MIGRATE'... Sorry if that question is off target... Best, Andre. -- Nothing is ever easy.

On Tue, Apr 14, 2009 at 2:09 PM, Andre Merzky <andre@merzky.net> wrote:
I have spent a large chunk of my weekend [2] roughing up the API and rather than bundling everything in together have so far opted for a core + extensions approach. ... [2] http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/APIDesign
Minor comments:
- I like the extension approach
Great! I was trying to come up with a way for us to have a minimalist core API (basically telling you how to find an end point, authenticate to it and interact with it) and then extend it where necessary. There's limitless possibilites for this architecture, though I've resisted the urge to list them for fear of being accused of trying to boil the ocean ;)
- do you intent to hook GLUE into the <Info> part in your XML example, or into similar places in the API? Optionally at least? <Info>4Gb, 2 CPU, 1 disk, 2 nic virtual machine</Info>
That's actually embedded OVF - what specifically did you have in mind?
- why the purl.org/occi namespace? OGF has an established namespace for XML schemata, see http://schemas.ogf.org/, and GFD.84 on http://www.ogf.org/docs/?cp
purl.org gives us a simple way to collaboratively develop the namespace while allowing for third party extensions, but I'm not particularly religious about it - we can migrate once the API settles down if we decide that's the best thing to do.
A question about the machine control extension: I am not overly familiar with the capabilities offerred by the various discussed backends, but is a 'CLONE' operation something which is being considered? That would be basically a CREATE op which refers to a running instance instead of reffering to an image and instance description (or whatever your CREATE needs as input). How would that map to your state machine? As suspend/resume (for the time a snapshot is taken)? Similar for 'MIGRATE'...
So my thoughts so far were that templates would be exposed as "ghosts" that would be missing "start", "stop", etc. actuators, rather having only "deploy" (ala Sun Cloud API). "clone" to me sounds like taking a copy of something that exists rather than instantiating something that is abstract, though perhaps something like this would be useful for snapshotting (ultimately we're going to have to run through various clients and see what functionality we're missing).
Sorry if that question is off target...
Definitely not - it's great to see some discussion kicking off already (we're still in the process of officially announcing the working group!). Sam

Quoting [Sam Johnston] (Apr 14 2009):
- do you intent to hook GLUE into the <Info> part in your XML example, or into similar places in the API? Optionally at least? <Info>4Gb, 2 CPU, 1 disk, 2 nic virtual machine</Info>
That's actually embedded OVF - what specifically did you have in mind?
Opps, sorry - I missed that, and barked up the wrong tree :-) Its obvious now, thanks. But anyway: do you expect GLUE to play any role in respect to the specification of (VM) resource requirements?
- why the [3]purl.org/occi namespace? OGF has an established namespace for XML schemata, see [4]http://schemas.ogf.org/, and GFD.84 on [5]http://www.ogf.org/docs/?cp
[6]purl.org gives us a simple way to collaboratively develop the namespace while allowing for third party extensions, but I'm not particularly religious about it - we can migrate once the API settles down if we decide that's the best thing to do.
fair enough.
A question about the machine control extension: I am not overly familiar with the capabilities offerred by the various discussed backends, but is a 'CLONE' operation something which is being considered? That would be basically a CREATE op which refers to a running instance instead of reffering to an image and instance description (or whatever your CREATE needs as input). How would that map to your state machine? As suspend/resume (for the time a snapshot is taken)? Similar for 'MIGRATE'...
So my thoughts so far were that templates would be exposed as "ghosts" that would be missing "start", "stop", etc. actuators, rather having only "deploy" (ala Sun Cloud API). "clone" to me sounds like taking a copy of something that exists rather than instantiating something that is abstract,
yes.
though perhaps something like this would be useful for snapshotting (ultimately we're going to have to run through various clients and see what functionality we're missing).
Thanks, makes sense.
Sorry if that question is off target...
Definitely not - it's great to see some discussion kicking off already (we're still in the process of officially announcing the working group!).
:-) Cheers, Andre. -- Nothing is ever easy.

Hey Andre - we reviewed GLUE in SLA@SOI to see if it would meet our needs for infrastructure provisioning but for the most our initial feelings are that it wouldn't suit. Would you have any other viewpoint on this? Andy <snip/> But anyway: do you expect GLUE to play any role in respect to the specification of (VM) resource requirements? <snip/> ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

Further to Andrew's comments, I've thus far tried to avoid fixed schemas for anything, preferring tags and attributes and deferring a lot of that detail to supporting standards like OVF. I don't see a problem with using GLUE as an "alternate" representation and/or linking to it using <link>s or an extension. I hope that answers your question... basically I suggest that we [re]use it if we need to but not before. Sam On Tue, Apr 14, 2009 at 2:36 PM, Edmonds, AndrewX <andrewx.edmonds@intel.com
wrote:
Hey Andre - we reviewed GLUE in SLA@SOI to see if it would meet our needs for infrastructure provisioning but for the most our initial feelings are that it wouldn't suit. Would you have any other viewpoint on this?
Andy
<snip/>
But anyway: do you expect GLUE to play any role in respect to the specification of (VM) resource requirements?
<snip/> ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

Hi Sam, Andrew, as Alexander and Alexis in the other branch of this thread (about scheduling), I just wanted to make sure that other OGF groups and standards get considered, and involved, *when appropriate*. So I'm happy to hear that people have considered to use GLUE, and that GLUE MAY be usable as alternative representation, etc. Quoting [Sam Johnston] (Apr 14 2009):
Further to Andrew's comments, I've thus far tried to avoid fixed schemas for anything, preferring tags and attributes and deferring a lot of that detail to supporting standards like OVF. I don't see a problem with using GLUE as an "alternate" representation and/or linking to it using <link>s or an extension. I hope that answers your question... basically I suggest that we [re]use it if we need to but not before. Sam
On Tue, Apr 14, 2009 at 2:36 PM, Edmonds, AndrewX <[1]andrewx.edmonds@intel.com> wrote:
Hey Andre - we reviewed GLUE in SLA@SOI to see if it would meet our needs for infrastructure provisioning but for the most our initial feelings are that it wouldn't suit. Would you have any other viewpoint on this? Andy
Andrew, would you be able to feed back to the GLUE WG where you considered the standarde to fall short of your requirements? They might be interested to learn about that.
But anyway: do you expect GLUE to play any role in respect to the specification of (VM) resource requirements?
I am actually not familiar enough with the topic to really have an educated opinion. As an observer, it seems that the OCCI will need to touch resource description at some point or the other, to specify requirements to a VM for example, and GLUE seems to aim at that type of use case. Not sure if any from the GLUE people are listening here. If not, it might be worthewhile to get their feedback at next OGF, by going to their session... Cheers, Andre. -- Nothing is ever easy.

Thanks Andre - I'll get around at some stage to supply some feedback to the GLUE WG, but EU deliverables take precedence for the moment ;-) I'd also agree on your point of requiring some means of resource description. Andy -----Original Message----- From: Andre Merzky [mailto:andremerzky@gmail.com] On Behalf Of Andre Merzky Sent: 14 April 2009 17:02 To: Sam Johnston Cc: Edmonds, AndrewX; Andre Merzky; occi-wg@ogf.org Subject: Re: [occi-wg] Scheduling parameters Hi Sam, Andrew, as Alexander and Alexis in the other branch of this thread (about scheduling), I just wanted to make sure that other OGF groups and standards get considered, and involved, *when appropriate*. So I'm happy to hear that people have considered to use GLUE, and that GLUE MAY be usable as alternative representation, etc. Quoting [Sam Johnston] (Apr 14 2009):
Further to Andrew's comments, I've thus far tried to avoid fixed schemas for anything, preferring tags and attributes and deferring a lot of that detail to supporting standards like OVF. I don't see a problem with using GLUE as an "alternate" representation and/or linking to it using <link>s or an extension. I hope that answers your question... basically I suggest that we [re]use it if we need to but not before. Sam
On Tue, Apr 14, 2009 at 2:36 PM, Edmonds, AndrewX <[1]andrewx.edmonds@intel.com> wrote:
Hey Andre - we reviewed GLUE in SLA@SOI to see if it would meet our needs for infrastructure provisioning but for the most our initial feelings are that it wouldn't suit. Would you have any other viewpoint on this? Andy
Andrew, would you be able to feed back to the GLUE WG where you considered the standarde to fall short of your requirements? They might be interested to learn about that.
But anyway: do you expect GLUE to play any role in respect to the specification of (VM) resource requirements?
I am actually not familiar enough with the topic to really have an educated opinion. As an observer, it seems that the OCCI will need to touch resource description at some point or the other, to specify requirements to a VM for example, and GLUE seems to aim at that type of use case. Not sure if any from the GLUE people are listening here. If not, it might be worthewhile to get their feedback at next OGF, by going to their session... Cheers, Andre. -- Nothing is ever easy. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

Dear All: I need some information about the back-end part of current Metascheduling for Clouds to provide some useful use-cases. In fact, at first, Is there any Metascheduler for Clouds? Can we classify OpenNebula as a Meta-scheduler for Clouds? If yes, what is its current policies, algorithms and optimization for Metascheduling in Clouds? On Tue, Apr 14, 2009 at 6:06 PM, Edmonds, AndrewX <andrewx.edmonds@intel.com> wrote:
Thanks Andre - I'll get around at some stage to supply some feedback to the GLUE WG, but EU deliverables take precedence for the moment ;-) I'd also agree on your point of requiring some means of resource description.
Andy
-----Original Message----- From: Andre Merzky [mailto:andremerzky@gmail.com] On Behalf Of Andre Merzky Sent: 14 April 2009 17:02 To: Sam Johnston Cc: Edmonds, AndrewX; Andre Merzky; occi-wg@ogf.org Subject: Re: [occi-wg] Scheduling parameters
Hi Sam, Andrew,
as Alexander and Alexis in the other branch of this thread (about scheduling), I just wanted to make sure that other OGF groups and standards get considered, and involved, *when appropriate*. So I'm happy to hear that people have considered to use GLUE, and that GLUE MAY be usable as alternative representation, etc.
Quoting [Sam Johnston] (Apr 14 2009):
Further to Andrew's comments, I've thus far tried to avoid fixed schemas for anything, preferring tags and attributes and deferring a lot of that detail to supporting standards like OVF. I don't see a problem with using GLUE as an "alternate" representation and/or linking to it using <link>s or an extension. I hope that answers your question... basically I suggest that we [re]use it if we need to but not before. Sam
On Tue, Apr 14, 2009 at 2:36 PM, Edmonds, AndrewX <[1]andrewx.edmonds@intel.com> wrote:
Hey Andre - we reviewed GLUE in SLA@SOI to see if it would meet our needs for infrastructure provisioning but for the most our initial feelings are that it wouldn't suit. Would you have any other viewpoint on this? Andy
Andrew, would you be able to feed back to the GLUE WG where you considered the standarde to fall short of your requirements? They might be interested to learn about that.
But anyway: do you expect GLUE to play any role in respect to the specification of (VM) resource requirements?
I am actually not familiar enough with the topic to really have an educated opinion. As an observer, it seems that the OCCI will need to touch resource description at some point or the other, to specify requirements to a VM for example, and GLUE seems to aim at that type of use case. Not sure if any from the GLUE people are listening here. If not, it might be worthewhile to get their feedback at next OGF, by going to their session...
Cheers, Andre.
-- Nothing is ever easy. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
-- Best Regards, Mehdi Sheikhalishahi

Dear Mehdi, About OpenNebula and Cloud infrastructures: - OpenNebula can be primarily used as a virtualization tool to manage your virtual infrastructure in the data-center or cluster. You know, this application is usually referred as private cloud, - With OpenNebula you can also dynamically scale it to multiple external clouds, so building a hybrid cloud. - When combined with a Cloud interface (Eucalyptus, Nimbus...) , OpenNebula can be used as engine for public clouds, providing a scalable and dynamic management of the back-end infrastructure. You can also use OpenNebula as Cloud Broker. In fact we are now executing some use cases across EC2 and ElasticHosts sites, without using local infrastructure. In this specific case, Reservoir is doing research on cross-site VM placement heuristics and algorithms different categories of parameters: –VEE requirements –SLAs –Local and remote resource availability –Performance measurements –Negotiation and placement decision time –Financial benefit 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 15/04/2009, at 12:56, Mehdi Sheikhalishahi wrote:
Dear All:
I need some information about the back-end part of current Metascheduling for Clouds to provide some useful use-cases. In fact, at first, Is there any Metascheduler for Clouds?
Can we classify OpenNebula as a Meta-scheduler for Clouds? If yes, what is its current policies, algorithms and optimization for Metascheduling in Clouds?
On Tue, Apr 14, 2009 at 6:06 PM, Edmonds, AndrewX <andrewx.edmonds@intel.com> wrote:
Thanks Andre - I'll get around at some stage to supply some feedback to the GLUE WG, but EU deliverables take precedence for the moment ;-) I'd also agree on your point of requiring some means of resource description.
Andy
-----Original Message----- From: Andre Merzky [mailto:andremerzky@gmail.com] On Behalf Of Andre Merzky Sent: 14 April 2009 17:02 To: Sam Johnston Cc: Edmonds, AndrewX; Andre Merzky; occi-wg@ogf.org Subject: Re: [occi-wg] Scheduling parameters
Hi Sam, Andrew,
as Alexander and Alexis in the other branch of this thread (about scheduling), I just wanted to make sure that other OGF groups and standards get considered, and involved, *when appropriate*. So I'm happy to hear that people have considered to use GLUE, and that GLUE MAY be usable as alternative representation, etc.
Quoting [Sam Johnston] (Apr 14 2009):
Further to Andrew's comments, I've thus far tried to avoid fixed schemas for anything, preferring tags and attributes and deferring a lot of that detail to supporting standards like OVF. I don't see a problem with using GLUE as an "alternate" representation and/or linking to it using <link>s or an extension. I hope that answers your question... basically I suggest that we [re]use it if we need to but not before. Sam
On Tue, Apr 14, 2009 at 2:36 PM, Edmonds, AndrewX <[1]andrewx.edmonds@intel.com> wrote:
Hey Andre - we reviewed GLUE in SLA@SOI to see if it would meet our needs for infrastructure provisioning but for the most our initial feelings are that it wouldn't suit. Would you have any other viewpoint on this? Andy
Andrew, would you be able to feed back to the GLUE WG where you considered the standarde to fall short of your requirements? They might be interested to learn about that.
But anyway: do you expect GLUE to play any role in respect to the specification of (VM) resource requirements?
I am actually not familiar enough with the topic to really have an educated opinion. As an observer, it seems that the OCCI will need to touch resource description at some point or the other, to specify requirements to a VM for example, and GLUE seems to aim at that type of use case. Not sure if any from the GLUE people are listening here. If not, it might be worthewhile to get their feedback at next OGF, by going to their session...
Cheers, Andre.
-- Nothing is ever easy. ------------------------------------------------------------- Intel Ireland Limited (Branch) Collinstown Industrial Park, Leixlip, County Kildare, Ireland Registered Number: E902934
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
-- Best Regards, Mehdi Sheikhalishahi _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
participants (8)
-
Alexander Papaspyrou
-
Alexis Richardson
-
Andre Merzky
-
Edmonds, AndrewX
-
Ignacio Martin Llorente
-
Mehdi Sheikhalishahi
-
Sam Johnston
-
Thijs Metsch