g/wiki/Heat/UI#Help_Text
>
> [4] Ex. Help Text accompanying a template in README.MD format:
> https://github.com/rackspace-orchestration-templates/docker
>
> -Keith
>
> From: Steven Dake
>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)
Excerpts from Mike Spreitzer's message of 2014-04-03 11:05:10 -0700:
> Clint Byrum wrote on 04/03/2014 01:10:30 PM:
>
> > Things that affect the stack as a whole really belong in the stack
> > API. That would also put them in the OS::Heat::Stack resource, so the
> > template language already supp
> 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 communit
Keith Bray wrote on 04/03/2014 01:50:28 PM:
> We proposed another specific piece of template data [3] which I
> can't remember whether it was met with resistance or we just didn't
> get to implementing it since we knew we would have to store other
> data specific to our uses cases in other fil
Clint Byrum wrote on 04/03/2014 01:10:30 PM:
> Things that affect the stack as a whole really belong in the stack
> API. That would also put them in the OS::Heat::Stack resource, so the
> template language already supports that.
The OS::Heat::Stack resource is one of several that create nested s
s.openstack.org>>
Date: Thursday, April 3, 2014 10:30 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [heat] metadata for a HOT
On 04/02/2014 08:41 PM, Keith Bray wrote:
https://wiki.
Excerpts from Mike Spreitzer's message of 2014-04-02 22:10:21 -0700:
> Zane Bitter wrote on 04/02/2014 05:36:43 PM:
>
> > I think that if you're going to propose a new feature, you should at
> > least give us a clue who you think is going to use it and what for ;)
>
> I was not eager to do that
Excerpts from Thomas Spatzier's message of 2014-04-03 08:36:20 -0700:
> > From: Mike Spreitzer
> > To: "OpenStack Development Mailing List \(not for usage questions\)"
> >
> > Date: 03/04/2014 07:10
> > Subject: Re: [openstack-dev] [heat] metadata
nstack-dev@lists.openstack.org>>
Date: Wednesday, April 2, 2014 9:31 PM
To: "OpenStack Development Mailing List (not for usage questions)"
<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [heat] metadata for a HOT
Is there any relevant wiki or spec
> 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 yo
Zane Bitter wrote on 04/02/2014 05:36:43 PM:
> I think that if you're going to propose a new feature, you should at
> least give us a clue who you think is going to use it and what for ;)
I was not eager to do that yet because I have not found a fully
satisfactory answer yet, at this point I a
dnesday, April 2, 2014 9:31 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [heat] metadata for a HOT
Is there any relevant wiki or specification doc?
2014-04-03 4:45 GMT+08:00 Mike Spre
Is there any relevant wiki or specification doc?
2014-04-03 4:45 GMT+08:00 Mike Spreitzer :
> I would like to suggest that a metadata section be allowed at the top
> level of a HOT. Note that while resources in a stack can have metadata,
> there is no way to put metadata on a stack itself. Wha
On 02/04/14 16:45, Mike Spreitzer wrote:
I would like to suggest that a metadata section be allowed at the top
level of a HOT. Note that while resources in a stack can have metadata,
there is no way to put metadata on a stack itself. What do you think?
I think that if you're going to propose
I would like to suggest that a metadata section be allowed at the top
level of a HOT. Note that while resources in a stack can have metadata,
there is no way to put metadata on a stack itself. What do you think?
Thanks,
Mike___
OpenStack-dev mailing
15 matches
Mail list logo
