Re: [Openstack] Allowing clients to pass capability requests through tags?

2011-02-11 Thread Eric Day
The main reason I was proposing full location/zone of objects is to allow this type of 'near' scheduling to happen without understanding what the actual object is. For example, imagine we want to start an instance near a particular swift object. We could query the swift object and in the metadata

Re: [Openstack] Allowing clients to pass capability requests through tags?

2011-02-11 Thread Jay Pipes
On Thu, Feb 10, 2011 at 7:21 PM, Brian Schott bfsch...@gmail.com wrote: Justin, Our USC-ISI team is very interested in this.  We are implementing different architecture types beyond x86_64.  We are also interested in suggesting switch topology for MPI cluster jobs, passing in requests for

Re: [Openstack] Allowing clients to pass capability requests through tags?

2011-02-11 Thread Sandy Walsh
@lists.launchpad.net; Devin Carlen Subject: Re: [Openstack] Allowing clients to pass capability requests through tags? Hi Sandy, I agree with using tags for full scheduler selection, it's something I've been pushing for from the start. The request contains any number of k/v pairs, the services provide

Re: [Openstack] Allowing clients to pass capability requests through tags?

2011-02-11 Thread Ken Pepple
On Feb 11, 2011, at 10:24 AM, Brian Schott wrote: Right now, we're switching on the label, which is I think is a bad idea. I need to capture this in a blueprint for Diablo, but what we're proposing is to expand the instance_types dictionary to include additional fields and possibly turn it

Re: [Openstack] Allowing clients to pass capability requests through tags?

2011-02-11 Thread Brian Schott
Ken, Absolutely. We would like to debate a few additional columns, but yes this is the right blueprint to work from. Brian Brian Schott bfsch...@gmail.com On Feb 11, 2011, at 1:54 PM, Ken Pepple wrote: On Feb 11, 2011, at 10:24 AM, Brian Schott wrote: Right now, we're switching on the

[Openstack] Allowing clients to pass capability requests through tags?

2011-02-10 Thread Justin Santa Barbara
Does anyone have any thoughts/objections on the blueprint I posted for allowing clients to pass capability-requests through tags? I'm planning on starting implementation soon, so if people think this is a bad idea I'd rather know before I start coding! Blueprint:

Re: [Openstack] Allowing clients to pass capability requests through tags?

2011-02-10 Thread Sandy Walsh
: openstack@lists.launchpad.net Subject: Re: [Openstack] Allowing clients to pass capability requests through tags? I think the blueprint was largely complementary to the multi-zone stuff; this is more about how the client _requests_ a particular location/capability through the API. The multi

Re: [Openstack] Allowing clients to pass capability requests through tags?

2011-02-10 Thread Brian Schott
Justin, Our USC-ISI team is very interested in this. We are implementing different architecture types beyond x86_64. We are also interested in suggesting switch topology for MPI cluster jobs, passing in requests for GPU accelerators, etc. Currently, our approach has been to specify these

Re: [Openstack] Allowing clients to pass capability requests through tags?

2011-02-10 Thread Justin Santa Barbara
Thanks Brian - that's a great suggestion for how to get round the limitations of the EC2 API. I've added it to the wiki page for the blueprint: *We could also stuff this information into another supported field; for example instance-type (e.g. euca-run-instance --instance-type