I like idea of scheduling actions overall. The idea of a generic scheduling
service also appeals to me a lot. The question is how do you generalize the
service. I'd love to see your write up.
-jOrGe W.
On Feb 16, 2011, at 4:35 PM, Adrian Otto wrote:
Glen,
I definitely recognize the value
On Feb 16, 2011, at 5:11 PM, Michael Mayo wrote:
> I like this idea, but I would suggest going with a unix timestamp in GMT
> instead of /2011/xx/xx/etc.
Whether you use a timestamp or MM... format, *always* use GMT. We
all know how much fun it is when someone in Europe sends a requ
Glen,
I definitely recognize the value in having scheduling capability. I wrote a
high level draft of a REST API for a generic scheduler to be used for batch job
processing. Scheduled events are discussed regularly by users of queue systems
that want certain things to happen on regular interval
On Wed, Feb 16, 2011 at 5:29 PM, Brian Waldon
wrote:
> -Original Message-
> From: "Jay Pipes"
> Sent: Wednesday, February 16, 2011 5:09pm
> To: "Glen Campbell"
> Cc: "openstack@lists.launchpad.net"
> Subject: Re: [Openstack] OpenStack Com
-Original Message-
From: "Jay Pipes"
Sent: Wednesday, February 16, 2011 5:09pm
To: "Glen Campbell"
Cc: "openstack@lists.launchpad.net"
Subject: Re: [Openstack] OpenStack Compute API 1.1 ‹ server actions
On Wed, Feb 16, 2011 at 5:02 PM, Glen Campbell
I like this idea, but I would suggest going with a unix timestamp in GMT
instead of /2011/xx/xx/etc.
Also, how would this effect error handling? It seems like you'd basically need
to have some sort of way to query all the server actions you've ever done
before with their HTTP responses.
On
On Wed, Feb 16, 2011 at 5:02 PM, Glen Campbell
wrote:
> The proposed compute API 1.1 has a specification for server actions (Sec.
> 4.4) with the endpoint:
>
> /servers/{id}/action
>
> The actual action is specified as the body of the POST request, and the
> implication is that the action is pe
The proposed compute API 1.1 has a specification for server actions (Sec. 4.4)
with the endpoint:
/servers/{id}/action
The actual action is specified as the body of the POST request, and the
implication is that the action is performed immediately, or as soon as possible.
I'd like us to cons
8 matches
Mail list logo
