://etherpad.openstack.org/p/juno-summit-heat-sw-orch
Regards,
Thomas
Steve Baker sba...@redhat.com wrote on 28/04/2014 23:31:56:
From: Steve Baker sba...@redhat.com
To: openstack-dev@lists.openstack.org
Date: 28/04/2014 23:32
Subject: Re: [openstack-dev] [Heat] Design summit preparation - Next
Excerpts from Steve Baker's message on 28/04/2014 01:25:29:
snip
#1 Enable software components for full lifecycle:
snip
So in a short, stripped-down version, SoftwareConfigs could look like
my_sw_config:
type: OS::Heat::SoftwareConfig
properties:
create_config: # the hook for
On 29/04/14 01:41, Thomas Spatzier wrote:
Excerpts from Steve Baker's message on 28/04/2014 01:25:29:
I'm with Clint on this one. Heat-engine cannot know the true state
of a server just by monitoring what has been polled and signaled.
Since it can't know it would be dangerous for it to guess.
On 23/04/14 04:42, Thomas Spatzier wrote:
Hi all,
following up on Zane's request from end of last week, I wanted to kick off
some discussion on the ML around a design summit session proposal titled
Next steps for Heat Software Orchestration. I guess there will be things
that can be sorted
On 24 Apr 2014, at 01:43, Ruslan Kamaldinov rkamaldi...@mirantis.com wrote:
On Tue, Apr 22, 2014 at 8:42 PM, Thomas Spatzier
thomas.spatz...@de.ibm.com wrote:
#2 Enable add-hoc actions on software components:
Cool, coincidentally or not but we use term “ad-hoc action” too in Mistral :)
This
preparation - Next
steps for Heat Software Orchestration
On 24 Apr 2014, at 01:43, Ruslan Kamaldinov rkamaldi...@mirantis.com
wrote:
On Tue, Apr 22, 2014 at 8:42 PM, Thomas Spatzier
thomas.spatz...@de.ibm.com wrote:
#2 Enable add-hoc actions on software components:
Cool, coincidentally
Excerpts from Thomas Spatzier's message of 2014-04-22 09:42:14 -0700:
Hi all,
following up on Zane's request from end of last week, I wanted to kick off
some discussion on the ML around a design summit session proposal titled
Next steps for Heat Software Orchestration. I guess there will
Hi Clint,
thanks for the comments. Those are some really good points. I added some
more thoughts from my side below.
Exceprts from Clint Byrum's message on 24/04/2014 17:53:40:
snip
So in a short, stripped-down version, SoftwareConfigs could look like
my_sw_config:
type:
On Tue, Apr 22, 2014 at 8:42 PM, Thomas Spatzier
thomas.spatz...@de.ibm.com wrote:
#2 Enable add-hoc actions on software components:
Apart from basic resource lifecycle hooks, it would be desirable to allow
for invocation of add-hoc actions on software. Examples would be the ad-hoc
creation of
Hi all,
following up on Zane's request from end of last week, I wanted to kick off
some discussion on the ML around a design summit session proposal titled
Next steps for Heat Software Orchestration. I guess there will be things
that can be sorted out this way and others that can be refined so
10 matches
Mail list logo
