client it is in a git repo. It could
>>>> then automatically look for repo information and set a stack metadata
>>>> item pointing back to it.
>>>
>>> Or just store the URL.
>>>
>>>> If you didn't care about taking a performance hit
>
>> Or just store the URL.
>>
>>> If you didn't care about taking a performance hit, heat client could
>>> always try and check to see if it was a git repo url. That may add
>>> several extra http requests though...
>>>
>>> Thanks,
>>> Kevin
>>>
> Kevin
>>
>> From: Clint Byrum [cl...@fewbar.com]
>> Sent: Wednesday, November 27, 2013 1:04 PM
>> To: openstack-dev
>> Subject: Re: [openstack-dev] [heat][horizon]Heat UI related
>>requirements & roadmap
>
esday, November 27, 2013 1:04 PM
To: openstack-dev
Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements &
roadmap
Excerpts from Fox, Kevin M's message of 2013-11-27 08:58:16 -0800:
This use case is sort of a providence case. Where did the stack come from so I
can
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:
> >
>
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
I have created the following wiki with all of the related use cases that
have been discussed in this thread as well as where I think we have
currently landed on the actual implementation for these use cases.
https://wiki.openstack.org/wiki/Heat/UI
I know that the first use case in particular, re
On 11/27/13 4:12 PM, "Steve Baker" wrote:
>On 11/28/2013 05:09 AM, Zane Bitter wrote:
>> On 26/11/13 22:24, Tim Schnell wrote:
>>> Use Case #1
>>> I see valid value in being able to group templates based on a type or
>>
>> +1, me too.
>>
>>> keyword. This would allow any client, Horizon or a Tem
stack-dev] [heat][horizon]Heat UI related requirements &
roadmap
Excerpts from Fox, Kevin M's message of 2013-11-27 08:58:16 -0800:
> This use case is sort of a providence case. Where did the stack come from so
> I can find out more about it.
>
This exhibits similar problems
On 11/27/2013 04:56 PM, Zane Bitter wrote:
On 27/11/13 19:57, Jay Pipes wrote:
Actually, even simpler than that...
parameters:
db:
- db_name:
description: blah
help: blah
- db_username:
description: blah
help: blah
After all, can't we assume that if the para
On 11/28/2013 05:09 AM, Zane Bitter wrote:
> On 26/11/13 22:24, Tim Schnell wrote:
>> Use Case #1
>> I see valid value in being able to group templates based on a type or
>
> +1, me too.
>
>> keyword. This would allow any client, Horizon or a Template Catalog
>> service, to better organize and hand
On 27/11/13 19:57, Jay Pipes wrote:
Actually, even simpler than that...
parameters:
db:
- db_name:
description: blah
help: blah
- db_username:
description: blah
help: blah
After all, can't we assume that if the parameter value is a list, then
it is a group of
Excerpts from Jay Pipes's message of 2013-11-27 10:57:56 -0800:
> On 11/27/2013 01:28 AM, Clint Byrum wrote:
> >> I propose adding an additional field to the parameter definition:
> >>
> >> Parameters:
> >> :
> >> description: This is the name of a nova key pair that will
Excerpts from Fox, Kevin M's message of 2013-11-27 08:58:16 -0800:
> This use case is sort of a providence case. Where did the stack come from so
> I can find out more about it.
>
This exhibits similar problems to our Copyright header problems. Relying
on authors to maintain their authorship inf
Excerpts from Tim Schnell's message of 2013-11-27 09:16:24 -0800:
>
> On 11/27/13 10:09 AM, "Zane Bitter" wrote:
>
> >On 26/11/13 22:24, Tim Schnell wrote:
> >> I propose adding an additional field to the parameter definition:
> >>
> >> Parameters:
> >> :
> >> descri
On 11/27/13 1:17 PM, "Zane Bitter" wrote:
>On 27/11/13 18:16, Tim Schnell wrote:
>>
>> On 11/27/13 10:09 AM, "Zane Bitter" wrote:
>>
>>> On 26/11/13 22:24, Tim Schnell wrote:
Use Case #1
I see valid value in being able to group templates based on a type or
>>>
>>> +1, me too.
>>>
On 27/11/13 18:16, Tim Schnell wrote:
On 11/27/13 10:09 AM, "Zane Bitter" wrote:
On 26/11/13 22:24, Tim Schnell wrote:
Use Case #1
I see valid value in being able to group templates based on a type or
+1, me too.
keyword. This would allow any client, Horizon or a Template Catalog
service
On 11/27/2013 01:28 AM, Clint Byrum wrote:
I propose adding an additional field to the parameter definition:
Parameters:
:
description: This is the name of a nova key pair that will be used
to
ssh to the compute instance.
help: To learn more about nova ke
On 27/11/13 18:12, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2013-11-27 08:09:33 -0800:
In the longer term, there seems to be a lot of demand for some sort of
template catalog service, like Glance for templates. (I disagree with
Clint that it should actually _be_ Glance the proje
On Wed, Nov 27 2013, Zane Bitter wrote:
>>
>> Parameters:
>> db_name:
>> group: db
>> order: 0
>> db_username:
>> group: db
>> order: 1
>> db_password:
>>
st (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements &
roadmap
You bring up a good point Thomas. I think some of the discussions are mixing
template and stack perspectives, they are not the same thin
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 Tim Schnell's message on 27.11.2013 00:44:04:
>>> From: Tim Schnell
>>> To: "OpenStack
m a design standpoint.
>>
>> Once keywords has been added to the template then part of the 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
On 11/27/13 10:09 AM, "Zane Bitter" wrote:
>On 26/11/13 22:24, Tim Schnell wrote:
>> Use Case #1
>> I see valid value in being able to group templates based on a type or
>
>+1, me too.
>
>> keyword. This would allow any client, Horizon or a Template Catalog
>> service, to better organize and han
Excerpts from Zane Bitter's message of 2013-11-27 08:09:33 -0800:
> In the longer term, there seems to be a lot of demand for some sort of
> template catalog service, like Glance for templates. (I disagree with
> Clint that it should actually _be_ Glance the project as we know it, for
> the reas
2.286.8977
From: Thomas Spatzier
To: "OpenStack Development Mailing List \(not for usage questions
\)" ,
Date: 11/27/2013 11:00 AM
Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements
&
M
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements &
roadmap
Ok, I just re-read my example and that was a terrible example. I'll try
and create the user story first and hopefully answer Clint's and Thomas&
hnell wrote on 27.11.2013 16:24:18:
> From: Tim Schnell
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 27.11.2013 16:28
> Subject: Re: [openstack-dev] [heat][horizon]Heat UI related
> requirements & roadmap
>
> Ok, I just re-read
On 11/27/13 10:39 AM, "Zane Bitter" wrote:
>On 26/11/13 23:44, Tim Schnell wrote:
>>> A template-validate call would need to return all the group and
>>>ordering
>>> >information, but otherwise heat can ignore this extra data.
>> I agree with all of your modifications, although bringing up the
>
On 26/11/13 23:44, Tim Schnell wrote:
A template-validate call would need to return all the group and ordering
>information, but otherwise heat can ignore this extra data.
I agree with all of your modifications, although bringing up the
template-validate call reminded me that the implementation
On 26/11/13 22:24, Tim Schnell wrote:
Use Case #1
I see valid value in being able to group templates based on a type or
+1, me too.
keyword. This would allow any client, Horizon or a Template Catalog
service, to better organize and handle display options for an end-user.
I believe these are
o let's ignore it for now.
Thanks,
Tim
On 11/27/13 3:19 AM, "Thomas Spatzier" wrote:
>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)"
>> ,
>
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, Chr
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 &
Excerpts from Ladislav Smola's message of 2013-11-26 06:04:12 -0800:
> Hello,
>
> seems too big to do the inline comments, so just a few notes here:
>
> If we truly want to have Templates portable, it would mean to have the
> 'metadata' somehow standardised, right?
Can you point to another port
Excerpts from Tim Schnell's message of 2013-11-26 13:24:22 -0800:
> So the originally question that I attempted to pose was, "Can we add a
> schema-less metadata section to the template that can be used for a
> variety of purposes?". It looks like the answer is no, we need to discuss
> the features
ist (not for usage questions)"
>>mailto:openstack-dev@lists.openstack.o
>>rg>>
>>Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements
>>& roadmap
>>
>>On Tue, Nov 26, 2013 at 3:24 PM, Tim Schnell
>>mailto:tim.schn...@racksp
uot;
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, November 26, 2013 4:02 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements &
ck.org>>
Date: Tuesday, November 26, 2013 4:02 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements &
roadmap
On Tue, Nov 26, 2013 at 3:24 P
On 11/26/13 4:16 PM, "Steve Baker" wrote:
>On 11/27/2013 10:24 AM, Tim Schnell wrote:
>> So the originally question that I attempted to pose was, "Can we add a
>> schema-less metadata section to the template that can be used for a
>> variety of purposes?". It looks like the answer is no, we need
"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements
> & roadmap
>
>On Tue, Nov 26, 2013 at 3:24 PM, Tim Schnell > wrote:
>
>>
nstack-dev@lists.openstack.org>"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements &
roadmap
On 11/27/2013 11:02 AM, Christopher Armstrong wrote:
On Tue, Nov 26, 2013 at 3:24 PM, Tim Schnell
mailto:tim.schn...@rackspace.com&
st (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements &
roadmap
On Tue, Nov 26, 2013 at 3:24 PM, Tim Schnell
mailto:tim.schn...@rackspace.com>> wrote:
So the originally question that I
On 11/27/2013 11:02 AM, Christopher Armstrong wrote:
> On Tue, Nov 26, 2013 at 3:24 PM, Tim Schnell
> mailto:tim.schn...@rackspace.com>> wrote:
>
>
>
> Use Case #3
> Grouping parameters would help the client make smarter decisions
> about how
> to display the parameters for input
On 11/27/2013 10:24 AM, Tim Schnell wrote:
> So the originally question that I attempted to pose was, "Can we add a
> schema-less metadata section to the template that can be used for a
> variety of purposes?". It looks like the answer is no, we need to discuss
> the features that would go in the m
On Tue, Nov 26, 2013 at 3:24 PM, Tim Schnell wrote:
> So the originally question that I attempted to pose was, "Can we add a
> schema-less metadata section to the template that can be used for a
> variety of purposes?". It looks like the answer is no, we need to discuss
> the features that would g
So the originally question that I attempted to pose was, "Can we add a
schema-less metadata section to the template that can be used for a
variety of purposes?". It looks like the answer is no, we need to discuss
the features that would go in the metadata section and add them to the HOT
specificati
On 26/11/13 03:26, Keith Bray wrote:
On 11/25/13 5:46 PM, "Clint Byrum" wrote:
Excerpts from Tim Schnell's message of 2013-11-25 14:51:39 -0800:
Hi Steve,
As one of the UI developers driving the requirements behind these new
blueprints I wanted to take a moment to assure you and the rest o
On Tue, Nov 26, 2013 at 03:04:12PM +0100, Ladislav Smola wrote:
> Hello,
>
> seems too big to do the inline comments, so just a few notes here:
>
> If we truly want to have Templates portable, it would mean to have
> the 'metadata' somehow standardised, right?
> Otherwise if every UI will add the
>
Date: Monday, November 25, 2013 11:47 PM
To: "openstack-dev@lists.openstack.org
<mailto:openstack-dev@lists.openstack.org>"
<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [heat][horizon]Heat UI related
requirements & roadmap
On 11/26/
ent Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, November 25, 2013 11:47 PM
To:
"openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>"
mailto:openstack-dev@lists.openstack.org>>
Subject
On 11/26/2013 03:26 PM, Keith Bray wrote:
>
> On 11/25/13 5:46 PM, "Clint Byrum" wrote:
>
>> Excerpts from Tim Schnell's message of 2013-11-25 14:51:39 -0800:
>>> Hi Steve,
>>>
>>> As one of the UI developers driving the requirements behind these new
>>> blueprints I wanted to take a moment to ass
On 11/25/13 5:46 PM, "Clint Byrum" wrote:
>Excerpts from Tim Schnell's message of 2013-11-25 14:51:39 -0800:
>> Hi Steve,
>>
>> As one of the UI developers driving the requirements behind these new
>> blueprints I wanted to take a moment to assure you and the rest of the
>> Openstack community
rom: Clint Byrum [cl...@fewbar.com]
Sent: Monday, November 25, 2013 3:46 PM
To: openstack-dev
Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements &
roadmap
Excerpts from Tim Schnell's message of 2013-11-25 14:51:39 -0800:
> Hi Steve,
>
> As one of the
Excerpts from Tim Schnell's message of 2013-11-25 14:51:39 -0800:
> Hi Steve,
>
> As one of the UI developers driving the requirements behind these new
> blueprints I wanted to take a moment to assure you and the rest of the
> Openstack community that the primary purpose of pushing these requireme
Hi Steve,
As one of the UI developers driving the requirements behind these new
blueprints I wanted to take a moment to assure you and the rest of the
Openstack community that the primary purpose of pushing these requirements
out to the community is to help improve the User Experience for Heat for
All,
So, lately we've been seeing more patches posted proposing added
functionality to Heat (the API and template syntax) related to
development of UI functionality.
This makes me both happy (because folks want to use Heat!) and sad (because
it's evident there are several proprietary UI's being d
57 matches
Mail list logo
