+1 on both from my side.
Regards,
Thomas
> From: "Sahdev P Zala"
> To: OpenStack Development Mailing List
> Date: 17/08/2015 21:38
> Subject: [openstack-dev] [heat-translator] Nominating new core reviewers
>
> Hello,
>
> I am glad to nominate Vahid Hashemian [1] and Srinivas Tadepalli [2]
> fo
+1 on both from me!
Cheers,
Thomas
> From: Steve Baker
> To: OpenStack Development Mailing List
> Date: 31/07/2015 06:37
> Subject: [openstack-dev] Proposing Kanagaraj Manickam and Ethan Lynn
> for heat-core
>
> I believe the heat project would benefit from Kanagaraj Manickam and
> Ethan Lynn h
> From: Jay Dobies
> To: openstack-dev@lists.openstack.org
> Date: 22/06/2015 19:22
> Subject: Re: [openstack-dev] [heat][tripleo]Recursive validation for
> easier composability
>
>
>
> On 06/22/2015 12:19 PM, Steven Hardy wrote:
> > Hi all,
> >
> > Lately I've been giving some thought to how we m
> From: Zane Bitter
> To: openstack Development Mailing List
> Date: 29/01/2015 17:47
> Subject: [openstack-dev] [Heat][Keystone] Native keystone resources in
Heat
>
> I got a question today about creating keystone users/roles/tenants in
> Heat templates. We currently support creating users via t
+1 on all changes.
Regards,
Thomas
> From: Angus Salkeld
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 28/01/2015 02:40
> Subject: [openstack-dev] [Heat] core team changes
>
> Hi all
> After having a look at the stats:
> http://stackalytics.com/report/contribut
> From: Steve Baker
> To: openstack-dev@lists.openstack.org
> Date: 12/01/2015 21:16
> Subject: Re: [openstack-dev] [heat][tripleo] Making diskimage-
> builder install from forked repo?
>
> On 09/01/15 07:06, Gregory Haynes wrote:
> > Excerpts from Steven Hardy's message of 2015-01-08 17:37:55 +00
Hi Yasunori,
you can submit a blueprint spec as a gerrit review to the heat-specs
repository [1].
I would suggest to have a look at some existing specs that already got
accepted to have an example for the format, important sections etc.
All kilo related specs are in a kilo sub-directory in the re
Excerpts from Steve Baker's message on 14/10/2014 23:52:41:
> Regarding the process of building base images, the currently documented
way
> [1] of using diskimage-builder turns out to be a bit unstable sometimes.
> Not because diskimage-builder is unstable, but probably because it pulls
in
> comp
Excerpts from Clint Byrum's message on 14/10/2014 23:38:46:
> >
> > Regarding the process of building base images, the currently documented
way
> > [1] of using diskimage-builder turns out to be a bit unstable
sometimes.
> > Not because diskimage-builder is unstable, but probably because it
pulls
Hi all,
I have been experimenting a lot with Heat software config to check out
what works today, and to think about potential next steps.
I've also worked on an internal project where we are leveraging software
config as of the Icehouse release.
I think what we can do now from a user's perspect
+1 !
> From: Zane Bitter
> To: OpenStack Development Mailing List
> Date: 06/10/2014 22:45
> Subject: [openstack-dev] [Heat] Nominating Pavlo Shchelokovskyy for
heat-core
>
> I'd like to propose that we add Pavlo Shchelokovskyy to the heat-core
team.
>
> Pavlo has been a consistently active memb
Excerpts from Steven Hardy's message on 23/09/2014 11:37:42:
> >
> > On the other hand, there is a big downside to having it (only) in Heat
also
> > - you're dependent on the operator deciding to provide it.
> >
> > >- You prempt the decision about integration with any higher
levelservices,
> > >
> From: Mike Spreitzer
> To: "OpenStack Development Mailing List \(not for usage questions\)"
>
> Date: 19/09/2014 07:15
> Subject: Re: [openstack-dev] [Heat] naming of provider template for docs
>
> Angus Salkeld wrote on 09/18/2014 09:33:56 PM:
>
> > Hi
>
> > I am trying to add some docs to op
> From: Tao Tao
> To: openstack-dev@lists.openstack.org
> Cc: Shu Tao , Yan Yan YY Hu
> , Bo B Yang
> Date: 01/08/2014 22:19
> Subject: [openstack-dev] [HEAT] Qestions on adding a new Software
> Config element for Opscode Chef
>
> Hi, All:
>
> We are trying to leverage Heat software config model
I think the problem could be that you need one network port for each
server, but you just have one OS::Neutron::Port resource defined.
wrote on 16/07/2014 08:17:00:
> From:
> To:
> Date: 16/07/2014 08:20
> Subject: [openstack-dev] heat stack-create with two vm instances
> always got one failed
> From: Pavlo Shchelokovskyy
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 14/07/2014 16:42
> Subject: [openstack-dev] [Heat] Nova-network support
>
> Hi Heaters,
>
> I would like to start a discussion about Heat and nova-network. As
> far as I understand nova-net
> From: Steven Hardy
> To: openstack-dev@lists.openstack.org
> Date: 07/07/2014 10:39
> Subject: [openstack-dev] [heat] Update behavior for CFN compatible
resources
>
> Hi all,
>
> Recently I've been adding review comments, and having IRC discussions
about
> changes to update behavior for CloudFor
> From: Steve Baker
> To: OpenStack Development Mailing List
> Date: 27/06/2014 00:10
> Subject: [openstack-dev] [heat] Sergey Kraynev for heat-core
>
> I'd like to nominate Sergey Kraynev for heat-core. His reviews are
> valuable and prolific, and his commits have shown a sound understanding
> o
Excerpt from Zane Bitter's message on 29/05/2014 20:57:10:
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org
> Date: 29/05/2014 20:59
> Subject: Re: [openstack-dev] [TripleO] [Ironic] [Heat] Mid-cycle
> collaborative meetup
> BTW one timing option I haven't seen mentioned is to follow
Excerpts from Lingxian Kong's message on 15/05/2014 22:51:33:
> From: Lingxian Kong
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 15/05/2014 22:53
> Subject: Re: [openstack-dev] Heat SoftwareConfig and SoftwareDevelopment
>
>
> Do you know any information about e
time for the session next Thursday.
[1] https://etherpad.openstack.org/p/juno-design-summit-heat-translator
Regards,
Thomas
> From: Thomas Spatzier/Germany/IBM@IBMDE
> To: "OpenStack Development Mailing List \(not for usage questions\)"
>
> Date: 06/05/2014 10:47
> Subjec
r Heat Software Orchestration
>
> 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 ha
-
> Dimitri
>
> [1] https://wiki.openstack.org/wiki/Heat/Vision
>
> On 05/05/14 19:21, "Thomas Spatzier" wrote:
>
> Hi all,
>
> I mentioned in some earlier mail that we have started to implement a
TOSCA
> YAML to HOT translator on stackforge as projec
Hi all,
I mentioned in some earlier mail that we have started to implement a TOSCA
YAML to HOT translator on stackforge as project "heat-translator". We have
been lucky to get a session allocated in the context of the "Open source @
OpenStack" program for the Atlanta summit, so I wanted to share
Excerpts from Steve Baker's message on 28/04/2014 01:25:29:
> #1 Enable software components for full lifecycle:
> So in a short, stripped-down version, SoftwareConfigs could look like
>
> my_sw_config:
> type: OS::Heat::SoftwareConfig
> properties:
> create_config: # the hook for softwar
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:
> > So in a short, stripped-down version, SoftwareConfigs could look like
> >
> > my_sw_config:
> > type: OS::Heat::
rchestration
>
>
> On 24 Apr 2014, at 01:43, Ruslan Kamaldinov
wrote:
>
> > On Tue, Apr 22, 2014 at 8:42 PM, Thomas Spatzier
> > wrote:
> >> #2 Enable add-hoc actions on software components:
>
> Cool, coincidentally or not but we use term “ad-hoc action” too i
enstack-dev@lists.openstack.org
> Date: 23/04/2014 07:56
> Subject: Re: [openstack-dev] [Heat] Proposing Thomas Spatzier for
heat-core
>
> +1 !
>
> On 04/23/2014 02:43 AM, Zane Bitter wrote:
> > Resending with [Heat] in the subject line. My bad.
> >
> > On 22/04/14 14:
Excerpts from Jay Pipes' message on 23/04/2014
01:43:42:
> On Tue, 2014-04-22 at 13:14 +0200, Thomas Spatzier wrote:
> >
> > > * Identify key/value pairs that are relied on by all of Nova to be a
> > > specific key and value combination, and make these things
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
Jay Pipes wrote on 20/04/2014 15:05:51:
> From: Jay Pipes
> To: openstack-dev@lists.openstack.org
> Date: 20/04/2014 15:07
> Subject: Re: [openstack-dev] [Nova][Neutron][Cinder][Heat]Should we
> support tags for os resources?
>
> On Sun, 2014-04-20 at 08:35 +, Huangtianhua wrote:
> > Hi all:
> From: Steve Baker
> To: openstack-dev@lists.openstack.org
> Date: 17/04/2014 00:55
> Subject: Re: [openstack-dev] [heat] [heat-templates] [qa] [tempest]
> Questions about images
>
> On 17/04/14 09:11, Thomas Spatzier wrote:
> >> From: Mike Spreitzer
> >>
> From: Mike Spreitzer
> To: "OpenStack Development Mailing List \(not for usage questions\)"
>
> Date: 16/04/2014 19:58
> Subject: Re: [openstack-dev] [heat] [heat-templates] [qa] [tempest]
> Questions about images
>
> Steven Hardy wrote answers to most of my questions.
>
> To clarify, my conce
emented on top things
> described above
>
> Murano, Heat teams, please let me know if this plan sounds sane to you.
>
> [0] https://blueprints.launchpad.net/heat/+spec/interface-types
>
> Thanks,
> Ruslan
>
> On Sat, Apr 5, 2014 at 12:25 PM, Thomas Spatzier
> wrote
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org
> Date: 16/04/2014 00:46
> Subject: Re: [openstack-dev] [heat] computed package names?
>
> On 15/04/14 17:59, Mike Spreitzer wrote:
> > Clint Byrum wrote on 04/15/2014 05:17:21 PM:
> > > Excerpts from Zane Bitter's message of 2014-04-15
> From: Steven Dake
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 16/04/2014 01:43
> Subject: Re: [openstack-dev] [heat] computed package names?
>
> On 04/15/2014 03:45 PM, Zane Bitter wrote:
> > On 15/04/14 17:59, Mike Spreitzer wrote:
> >> Clint Byrum wrote on
> From: Steven Dake
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 07/04/2014 21:45
> Subject: Re: [openstack-dev] [heat] Managing changes to the Hot
> Specification (hot_spec.rst)
>
> On 04/07/2014 11:01 AM, Zane Bitter wrote:
> > On 06/04/14 14:23, Steven Dake wr
> From: Steve Baker
> To: openstack-dev@lists.openstack.org
> Date: 06/04/2014 22:32
> Subject: Re: [openstack-dev] [heat] Managing changes to the Hot
> Specification (hot_spec.rst)
>
> On 07/04/14 06:23, Steven Dake wrote:
> > Hi folks,
> >
> > There are two problems we should address regarding t
Clint Byrum wrote on 04/04/2014 19:05:04:
> From: Clint Byrum
> To: openstack-dev
> Date: 04/04/2014 19:06
> Subject: Re: [openstack-dev] [Heat] [Murano] [Solum] applications inthe
cloud
>
> Excerpts from Stan Lagun's message of 2014-04-04 02:54:05 -0700:
> > Hi Steve, Thomas
> >
> > I'm glad th
Hi Steve,
your indexing idea sounds interesting, but I am not sure it would work
reliably. The kind of matching based on names of parameters and outputs and
internal get_attr uses has very strong assumptions and I think there is a
not so low risk of false positives. What if the templates includes
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org
> Date: 03/04/2014 22:09
> Subject: Re: [openstack-dev] [Heat] Some thoughts on the mapping section
>
> On 03/04/14 03:21, Thomas Herve wrote:
> >> Speaking of offering options for selection, there is another proposal
on
> >> >adding cond
> From: Keith Bray
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 03/04/2014 19:51
> Subject: Re: [openstack-dev] [heat] metadata for a HOT
>
> Steve, agreed. Your description I believe is the conclusion that
> the community came to when this was perviously discus
Excerpts from Thomas Herve's message on 03/04/2014 09:21:05:
> From: Thomas Herve
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 03/04/2014 09:21
> Subject: Re: [openstack-dev] [Heat] Some thoughts on the mapping section
>
>
> > Speaking of offering options for
> From: Mike Spreitzer
> To: "OpenStack Development Mailing List \(not for usage questions\)"
>
> Date: 03/04/2014 07:10
> Subject: Re: [openstack-dev] [heat] metadata for a HOT
>
> Zane Bitter wrote on 04/02/2014 05:36:43 PM:
>
> > I think that if you're going to propose a new feature, you shou
;re doing right now with
> TOSCA-compliant layer?
> We would like to join to this effort.
>
> Thanks,
> Dmitry
>
> On Wed, Mar 26, 2014 at 10:38 AM, Thomas Spatzier
> wrote:
> Excerpt from Zane Bitter's message on 26/03/2014 02:26:42:
>
> > From: Zane Bit
Excerpt from Zane Bitter's message on 26/03/2014 02:26:42:
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org
> Date: 26/03/2014 02:27
> Subject: Re: [openstack-dev] [Murano][Heat] MuranoPL questions?
>
> > Cloud administrators are usually technical guys that are capable of
> > learni
Shaunak Kashyap wrote on 21/03/2014
05:26:50:
> From: Shaunak Kashyap
> To: "openstack-dev@lists.openstack.org"
> Date: 21/03/2014 05:29
> Subject: [openstack-dev] [Heat] Resource dependencies
>
> Hi,
>
> In a Heat template, what does it mean for a resource to depend on
> another resource? As i
Just out of curiosity: what is the purpose of project "warm"? From the wiki
page and the sample it looks pretty much like what Heat is doing.
And "warm" is almost "HOT" so could you imagine your use cases can just be
addressed by Heat using HOT templates?
Regards,
Thomas
sahid wrote on 18/03/201
Excerpts from Zane Bitter's message on 19/03/2014 18:18:34:
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org
> Date: 19/03/2014 18:21
> Subject: Re: [openstack-dev] [Murano][Heat] MuranoPL questions?
>
> On 19/03/14 05:00, Stan Lagun wrote:
> > Steven,
> >
> > Agree with your opinion o
Randall Burt wrote on 10/03/2014 19:51:58:
> From: Randall Burt
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 10/03/2014 19:55
> Subject: Re: [openstack-dev] [Heat][Murano][TOSCA] Murano team
> contrib. to Heat TOSCA activities
>
>
> On Mar 10, 2014, at 1:26 PM,
Forgot to provide the email addresses of Paul and Simon in my last mail:
paul.lip...@ca.com
smo...@de.ibm.com
Regards,
Thomas
> From: Thomas Spatzier/Germany/IBM@IBMDE
> To: "OpenStack Development Mailing List \(not for usage questions\)"
>
> Date: 05/03/2014 10:21
>
Hi Stan,
thanks for sharing your thoughts about Murano and relation to TOSCA. I have
added a few comments below.
> From: Stan Lagun
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 05/03/2014 00:51
> Subject: Re: [openstack-dev] Incubation Request: Murano
>
> Hi al
ww.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca
[2] https://github.com/stackforge/heat-translator
Regards,
Thomas
>
> Thanks
> Georgy
>
> On Tue, Mar 4, 2014 at 2:36 PM, Thomas Spatzier
> wrote:
> Excerpt from Zane Bitter's message on 04/03/2014 23:16:21:
> > F
Excerpt from Zane Bitter's message on 04/03/2014 23:16:21:
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org
> Date: 04/03/2014 23:20
> Subject: Re: [openstack-dev] Incubation Request: Murano
>
> On 04/03/14 00:04, Georgy Okrokvertskhov wrote:
> >
> It so happens that the OASIS's TOSCA t
Hi all,
I would like to pick up the TOSCA topic brought up by Zane in his mail
below.
TOSCA is in fact a standard that seems closely aligned with the concepts
that Murano is implementing, so thanks Zane for bringing up this
discussion. I saw Georgy's reply early today where he stated that Murano
Hi Qiming,
not sure if you have already seen it, but there is some documentation
available at the following locations. If you already know it, sorry for
dup ;-)
Entry to Heat documentation:
http://docs.openstack.org/developer/heat/
Template Guide with pointers to more details like documentation
Hi Clint,
thanks for writing this down. This is a really interesting use case and
feature, also in relation to what was recently discussed on rolling
updates.
I have a couple of thoughts and questions:
1) The overall idea seems clear to me but I have problems understanding the
detailed flow and
Thomas Herve wrote on 03/02/2014 21:46:05:
> From: Thomas Herve
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 03/02/2014 21:52
> Subject: Re: [openstack-dev] [Heat] [TripleO] Rolling updates spec
> re-written. RFC
>
> > So, I wrote the original rolling updates sp
Hi Thomas,
I haven't looked at the details of the autoscaling design for a while, but
the first option looks more intuitive to me.
It seems to cover the same content as LaunchConfiguration, but is it
generic and therefore would provide for one common approach for all kinds
of resources.
Regards,
Zane Bitter wrote on 27.11.2013 22:56:16:
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org,
> Date: 27.11.2013 23:00
> Subject: Re: [openstack-dev] [heat][horizon]Heat UI related
> requirements & roadmap
>
> On 27/11/13 19:57, Jay Pipes wrote:
> >
> > Actually, even simpler than that.
Excerpts from Zane Bitter's message on 27.11.2013 20:17:56:
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org,
> Date: 27.11.2013 20:21
> Subject: Re: [openstack-dev] [heat][horizon]Heat UI related
> requirements & roadmap
>
> On 27/11/13 18:16, Tim Schnell wrote:
> >
> > On 11/27/13 10:
blueprint
> would be to return it with the stack-list information.
>
> The previous example I attempted to explain is really more of an edge
> case, so let's ignore it for now.
>
> Thanks,
> Tim
>
> On 11/27/13 3:19 AM, "Thomas Spatzier"
wrote:
>
>
Excerpts from Steve Baker's message on 26.11.2013 23:29:06:
> From: Steve Baker
> To: openstack-dev@lists.openstack.org,
> Date: 26.11.2013 23:32
> Subject: Re: [openstack-dev] [heat][horizon]Heat UI related
> requirements & roadmap
>
> On 11/27/2013 11:02 AM, Christopher Armstrong wrote:
> On Tu
Excerpts from Tim Schnell's message on 27.11.2013 00:44:04:
> From: Tim Schnell
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 27.11.2013 00:47
> Subject: Re: [openstack-dev] [heat][horizon]Heat UI related
> requirements & roadmap
>
>
> That is not the use case
Steve Baker wrote on 21.11.2013 21:19:07:
> From: Steve Baker
> To: openstack-dev@lists.openstack.org,
> Date: 21.11.2013 21:25
> Subject: Re: [openstack-dev] [Heat] HOT software configuration
> refined after design summit discussions
>
> On 11/21/2013 08:48 PM,
Excerpts from Steve Baker's message on 21.11.2013 00:00:47:
> From: Steve Baker
> To: openstack-dev@lists.openstack.org,
> Date: 21.11.2013 00:04
> Subject: Re: [openstack-dev] [Heat] HOT software configuration
> refined after design summit discussions
>
> On 11/21/2013 11:41 AM, Clint Byrum wrote
Steve Baker wrote on 20.11.2013 09:51:34:
> From: Steve Baker
> To: openstack-dev@lists.openstack.org,
> Date: 20.11.2013 09:55
> Subject: Re: [openstack-dev] [Heat] HOT software configuration
> refined after design summit discussions
>
> On 11/20/2013 09:29 PM, Clint Byrum wrote:
> > Excerpts fr
Excerpts from Steve Baker's message on 19.11.2013 21:40:54:
> From: Steve Baker
> To: openstack-dev@lists.openstack.org,
> Date: 19.11.2013 21:43
> Subject: Re: [openstack-dev] [Heat] HOT software configuration
> refined after design summit discussions
>
> I think there needs to a CM tool specifi
Steve Baker wrote on 18.11.2013 21:52:04:
> From: Steve Baker
> To: openstack-dev@lists.openstack.org,
> Date: 18.11.2013 21:54
> Subject: Re: [openstack-dev] [Heat] HOT software configuration
> refined after design summit discussions
>
> On 11/19/2013 02:22 AM, Thomas Spatz
Hi all,
I have reworked the wiki page [1] I created last week to reflect
discussions we had on the mail list and in IRC. From ML discussions last
week it looked like we were all basically on the same page (with some
details to be worked out), and I hope the new draft eliminates some
confusion that
Hi Bartosz,
one thing that is still not clear to me:
In the discussion at the summit and in your updated architecture on the
wiki it talks about two Heat engines, one in each region, and on-top only
the dashboard. So what entity will really do the cross region
orchestration? In the discussions I h
Zane Bitter wrote on 13.11.2013 18:11:18:
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org,
> Date: 13.11.2013 18:14
> Subject: Re: [openstack-dev] [Heat] HOT software configuration
> refined after design summit discussions
>
> On 11/11/13 17:57, Thomas Spatzier
Excerpts from Clint Byrum's message on 13.11.2013 09:59:56:
> From: Clint Byrum
> To: openstack-dev ,
> Date: 13.11.2013 10:03
> Subject: Re: [openstack-dev] [Heat] HOT software configuration
> refined after design summit discussions
>
> Excerpts from Thomas Spatzier's message of 2013-11-13 00:28:
Angus Salkeld wrote on 12.11.2013 23:05:57:
> From: Angus Salkeld
> To: openstack-dev@lists.openstack.org,
> Date: 12.11.2013 23:09
> Subject: Re: [openstack-dev] [Mistral] really simple workflow for
> Heat configuration tasks
>
> On 12/11/13 13:04 +0100, Thomas Spatzi
Angus Salkeld wrote on 13.11.2013 00:22:44:
> From: Angus Salkeld
> To: openstack-dev@lists.openstack.org,
> Date: 13.11.2013 00:25
> Subject: Re: [openstack-dev] [Heat] HOT software configuration
> refined after design summit discussions
>
> On 12/11/13 10:32 -0800, Clint Byrum wrote:
> >Excerpt
Georgy Okrokvertskhov wrote on 12.11.2013
21:27:13:
> From: Georgy Okrokvertskhov
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 12.11.2013 21:29
> Subject: Re: [openstack-dev] [Heat] HOT software configuration
> refined after design summit discussions
>
> Hi,
>
Excerpts form Clint Byrum's message on 12.11.2013 19:32:50:
> From: Clint Byrum
> To: openstack-dev ,
> Date: 12.11.2013 19:35
> Subject: Re: [openstack-dev] [Heat] HOT software configuration
> refined after design summit discussions
>
> Excerpts from Thomas Spatzier's message of 2013-11-11 08:57:
Hi Angus,
that is an interesting idea. Since you mentioned the software config
proposal in the beginning as a related item, I guess you are trying to
solve some software config related issues with Mistral. So a few questions,
looking at this purely from a software config perspect:
Are you thinkin
Hi all,
I have just posted the following wiki page to reflect a refined proposal
for HOT software configuration based on discussions at the design summit
last week. Angus also put a sample up in an etherpad last week, but we did
not have enough time to go thru it in the design session. My write-u
Zane Bitter wrote on 30.10.2013 22:33:31:
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org,
> Date: 30.10.2013 22:36
> Subject: Re: [openstack-dev] [Heat] Comments on Steve Baker's
> Proposal on HOT Software Config
>
> On 30/10/13 20:35, Lakshminaraya Renganarayana wrote:
> > >I'd lik
Hi all,
I have read thru all the good discussion around software orchestration and
what to share my view. I see that there are two threads - this one and [1]
- but I am just replying to the one with the more generic topic line.
So on the recent twist to have software components implemented as
res
o the
one
> who was vocal at the Portland summit about the need for HOT syntax. I
> think both projects are on a good path with a lot of fun collaboration
> time ahead.
>
> Kind regards,
> -Keith
>
> On 10/24/13 7:56 AM, "Thomas Spatzier"
wrote:
>
> &
Hi Adrian,
really intersting! I wonder what the relation to all the software
orchestration in Heat discussions is that have been going on for a while
now.
Regards,
Thomas
Adrian Otto wrote on 23.10.2013 21:03:10:
> From: Adrian Otto
> To: OpenStack Development Mailing List
,
> Date: 23.10.2013
Hi all,
maybe a bit off track with respect to latest concrete discussions, but I
noticed the announcement of project "Solum" on openstack-dev.
Maybe this is playing on a different level, but I still see some relation
to all the software orchestration we are having. What are your opinions on
this?
Clint Byrum wrote on 23.10.2013 00:28:17:
> From: Clint Byrum
> To: openstack-dev ,
> Date: 23.10.2013 00:30
> Subject: Re: [openstack-dev] [Heat] HOT Software configuration proposal
>
> Excerpts from Georgy Okrokvertskhov's message of 2013-10-22 13:32:40
-0700:
> > Hi Thomas,
> >
> > I agree wit
ition? I mean how does the system know what exactly MySQL is
> and how to install it? What MySQL version is it gonna be? Will it be
> x86 or x64? How does the system understand that I need MySQL for
> Windows on Windows VM rather then Linux MySQL? What do I as a
> developer need to d
sed.
> and how to install it? What MySQL version is it gonna be? Will it be
> x86 or x64? How does the system understand that I need MySQL for
> Windows on Windows VM rather then Linux MySQL? What do I as a
> developer need to do so that it would be possible to have "type:
>
Zane Bitter wrote on 22.10.2013 17:23:52:
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org,
> Date: 22.10.2013 17:26
> Subject: Re: [openstack-dev] [Heat] HOT Software configuration proposal
>
> On 22/10/13 16:35, Thomas Spatzier wrote:
> > Zane Bitter wrot
Zane Bitter wrote on 22.10.2013 15:24:28:
> From: Zane Bitter
> To: openstack-dev@lists.openstack.org,
> Date: 22.10.2013 15:27
> Subject: Re: [openstack-dev] [Heat] HOT Software configuration proposal
>
> On 22/10/13 09:15, Thomas Spatzier wrote:
> > BTW, the conven
> Steve Baker wrote on 21.10.2013 23:02:47:
> From: Steve Baker
> To: openstack-dev@lists.openstack.org,
> Date: 21.10.2013 23:06
> Subject: Re: [openstack-dev] [Heat] HOT Software configuration proposal
>
>> On 10/22/2013 08:45 AM, Mike Spreitzer wrote:
>> Steve Baker wrote on 10/15/2013 06:48:
Hi Lakshmi,
you mentioned an example in your original post, but I did not find it. Can
you add the example?
Lakshminaraya Renganarayana wrote on 18.10.2013
20:57:43:
> From: Lakshminaraya Renganarayana
> To: OpenStack Development Mailing List
,
> Date: 18.10.2013 21:01
> Subject: Re: [openstack
Hi Steve,
thanks a lot taking the effort to write all this down. I had a look at both
wiki pages and have some comments below. This is really from the top of my
head, and I guess I have to spend some more time thinking about it, but I
wanted to provide some feedback anyway.
On "components vs. res
Steven Dake wrote on 11.10.2013 21:02:38:
> From: Steven Dake
> To: OpenStack Development Mailing List
,
> Date: 11.10.2013 21:04
> Subject: Re: [openstack-dev] [Heat] HOT Software orchestration
> proposal for workflows
>
> On 10/11/2013 11:55 AM, Lakshminaraya Renganarayana wrote:
> Clint Byrum
Hi all,
Lakshminaraya Renganarayana wrote on 10.10.2013
01:34:41:
> From: Lakshminaraya Renganarayana
> To: Joshua Harlow ,
> Cc: OpenStack Development Mailing List
> Date: 10.10.2013 01:37
> Subject: Re: [openstack-dev] [Heat] HOT Software orchestration
> proposal for workflows
>
> Hi Joshua,
Excerpts from Clint Byrum's message
> From: Clint Byrum
> To: openstack-dev ,
> Date: 09.10.2013 03:54
> Subject: Re: [openstack-dev] [Heat] HOT Software orchestration
> proposal for workflows
>
> Excerpts from Stan Lagun's message of 2013-10-08 13:53:45 -0700:
> > Hello,
> >
> >
> > That is why
Thomas Hervé wrote on 03.10.2013 09:59:02:
> From: Thomas Hervé
> To: OpenStack Development Mailing List
,
> Date: 03.10.2013 10:01
> Subject: Re: [openstack-dev] [Heat] Autoscale and load balancers
>
>
> On Wed, Oct 2, 2013 at 11:07 PM, Thomas
Spatzier > wrote:
>
Thomas Hervé wrote on 02.10.2013 17:06:48:
> From: Thomas Hervé
> To: OpenStack Development Mailing List
,
> Date: 02.10.2013 17:09
> Subject: [openstack-dev] [Heat] Autoscale and load balancers
>
> Hi all,
>
> There is a small but important part of the autoscale design described in
> https://wi
Clint Byrum wrote on 01.10.2013 08:31:44 - Excerpt:
> From: Clint Byrum
> To: openstack-dev ,
> Date: 01.10.2013 08:33
> Subject: Re: [openstack-dev] [heat] [scheduler] Bringing things
> together for Icehouse (now featuring software orchestration)
>
> Excerpts from Georgy Okrokvertskhov's messag
Excerpt from Clint's mail on 25.09.2013 22:23:07:
>
> I think we already have some summit suggestions for discussing HOT,
> it would be good to come prepared with some visions for the future
> of HOT so that we can hash these things out, so I'd like to see this
> discussion continue.
Absolutely!
Clint Byrum wrote on 25.09.2013 08:46:57:
> From: Clint Byrum
> To: openstack-dev ,
> Date: 25.09.2013 08:48
> Subject: Re: [openstack-dev] [heat] [scheduler] Bringing things
> together for Icehouse (now featuring software orchestration)
>
> Excerpts from Mike Spreitzer's message of 2013-09-24 22
1 - 100 of 102 matches
Mail list logo
