[lots of points about resource manipulation APIs, templates, autoscaling
design, and so forth...]
I'm glad so many people got involved in this thread :-) I really appreciate
the feedback. I think we can continue with autoscale design work without
relying on resource manipulation APIs. There are ce
On 19/06/13 06:41, Christopher Armstrong wrote:
On Tue, Jun 18, 2013 at 11:01 PM, Adrian Otto mailto:adrian.o...@rackspace.com>> wrote:
On Jun 18, 2013, at 6:09 PM, Angus Salkeld mailto:asalk...@redhat.com>> wrote:
> To me one of the most powerful and apealing things of Heat is the
On 19/06/13 06:01, Adrian Otto wrote:
Angus,
I'm glad you are asking good questions. I have additional input for you to
consider below.
On Jun 18, 2013, at 6:09 PM, Angus Salkeld wrote:
On 18/06/13 23:32 +, Adrian Otto wrote:
Yes. I think having a POST method in the API makes perfect s
On Wed, Jun 19, 2013 at 04:01:24AM +, Adrian Otto wrote:
> Angus,
>
> I'm glad you are asking good questions. I have additional input for you to
> consider below.
>
> On Jun 18, 2013, at 6:09 PM, Angus Salkeld wrote:
>
> > On 18/06/13 23:32 +, Adrian Otto wrote:
> >> Yes. I think havin
On 19/06/13 01:32, Adrian Otto wrote:
Yes. I think having a POST method in the API makes perfect sense. Assuming we
reach agreement on that, the next question that comes up is:
How to do you modify resources that have been created with a POST?
You mention HTTP PUT as an answer to that. Unfortu
On 19 June 2013 16:01, Adrian Otto wrote:
> It's also useful for situations like rolling updates, for when a complete
> redeployment is not practical, affordable, or desirable. Think of this as the
> point of intersection between a configuration management system and the
> orchestration system.
Angus Salkeld wrote on 19.06.2013 03:09:34:
> From: Angus Salkeld
> To: openstack-dev@lists.openstack.org,
> Date: 19.06.2013 03:19
> Subject: Re: [openstack-dev] [Heat] Does it make sense to have a
> resource-create API?
>
> On 18/06/13 23:32 +, Adrian Otto wrote:
>
On Tue, Jun 18, 2013 at 11:01 PM, Adrian Otto wrote:
> On Jun 18, 2013, at 6:09 PM, Angus Salkeld wrote:
> > To me one of the most powerful and apealing things of Heat is the
> > ability to reproducibly re-create a stack from a template. This
> > new public API is going to make this difficult.
>
Angus,
I'm glad you are asking good questions. I have additional input for you to
consider below.
On Jun 18, 2013, at 6:09 PM, Angus Salkeld wrote:
> On 18/06/13 23:32 +, Adrian Otto wrote:
>> Yes. I think having a POST method in the API makes perfect sense. Assuming
>> we reach agreement
On Jun 18, 2013, at 8:18 PM, Christopher Armstrong
wrote:
> Hi Adrian, thanks for the response. I'll just respond to one thing
> right now (since it's way after hours for me ;)
>
> On Tue, Jun 18, 2013 at 6:32 PM, Adrian Otto
> wrote:
>> On Jun 18, 2013, at 3:44 PM, Christopher Armstrong
>
Hi Adrian, thanks for the response. I'll just respond to one thing
right now (since it's way after hours for me ;)
On Tue, Jun 18, 2013 at 6:32 PM, Adrian Otto wrote:
> On Jun 18, 2013, at 3:44 PM, Christopher Armstrong
>
> wrote:
>
>> tl;dr POST /$tenant/stacks/$stack/resources/ ?
>
> Yes.
[
On 18/06/13 23:32 +, Adrian Otto wrote:
Yes. I think having a POST method in the API makes perfect sense. Assuming we
reach agreement on that, the next question that comes up is:
Err, I am not convinced.
Before that, I think it's worth highlighting the different
proposals/requirements he
Yes. I think having a POST method in the API makes perfect sense. Assuming we
reach agreement on that, the next question that comes up is:
How to do you modify resources that have been created with a POST?
You mention HTTP PUT as an answer to that. Unfortunately PUT is only really
useful for do
tl;dr POST /$tenant/stacks/$stack/resources/ ?
== background ==
While thinking about the Autoscaling API, Thomas Hervé and I had the
following consideration:
- autoscaling is implemented as a set of Heat Resources
- there are already general APIs for looking at resources generically:
- resour
14 matches
Mail list logo
