Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-12-06 Thread Randall Burt
: Wednesday, 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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-12-06 Thread Tim Schnell
http requests though... Thanks, 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 Excerpts from Fox, Kevin

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-28 Thread Zane Bitter
, 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 find out more

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Thomas Spatzier
Excerpts from Tim Schnell's message on 27.11.2013 00:44:04: From: Tim Schnell tim.schn...@rackspace.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org, Date: 27.11.2013 00:47 Subject: Re: [openstack-dev] [heat][horizon]Heat UI related

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Thomas Spatzier
Excerpts from Steve Baker's message on 26.11.2013 23:29:06: From: Steve Baker sba...@redhat.com 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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Tim Schnell
-dev] [heat][horizon]Heat UI related requirements roadmap snip That is not the use case that I'm attempting to make, let me try again. For what it's worth I agree, that in this use case I want a mechanism to tag particular versions of templates your solution makes sense and will probably

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Zane Bitter
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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Tim Schnell
On 11/27/13 10:39 AM, Zane Bitter zbit...@redhat.com 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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Fox, Kevin M
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's concerns. If the only use

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Edmund Troche
) openstack-dev@lists.openstack.org, Date: 27.11.2013 00:47 Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap snip That is not the use case that I'm attempting to make, let me try again. For what it's worth I agree, that in this use case I want

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Clint Byrum
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 reasons

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Tim Schnell
On 11/27/13 10:09 AM, Zane Bitter zbit...@redhat.com 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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Tim Schnell
) openstack-dev@lists.openstack.org, Date: 27.11.2013 16:28 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's concerns

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Tim Schnell
00:47 Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap snip That is not the use case that I'm attempting to make, let me try again. For what it's worth I agree, that in this use case I want a mechanism to tag particular versions of templates your solution

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Tim Schnell
Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto: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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Jason Dunsmore
On Wed, Nov 27 2013, Zane Bitter wrote: Parameters: db_name: group: db order: 0 db_username: group: db order: 1 db_password: group: db

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Zane Bitter
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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Jay Pipes
On 11/27/2013 01:28 AM, Clint Byrum wrote: I propose adding an additional field to the parameter definition: Parameters: parameter name: description: This is the name of a nova key pair that will be used to ssh to the compute instance. help: To learn

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Zane Bitter
On 27/11/13 18:16, Tim Schnell wrote: On 11/27/13 10:09 AM, Zane Bitter zbit...@redhat.com 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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Tim Schnell
On 11/27/13 1:17 PM, Zane Bitter zbit...@redhat.com wrote: On 27/11/13 18:16, Tim Schnell wrote: On 11/27/13 10:09 AM, Zane Bitter zbit...@redhat.com 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.

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Clint Byrum
Excerpts from Tim Schnell's message of 2013-11-27 09:16:24 -0800: On 11/27/13 10:09 AM, Zane Bitter zbit...@redhat.com wrote: On 26/11/13 22:24, Tim Schnell wrote: I propose adding an additional field to the parameter definition: Parameters: parameter name:

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Clint Byrum
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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Clint Byrum
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: parameter name: description: This is the name of a nova key pair that will

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Zane Bitter
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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Steve Baker
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 handle display

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Jay Pipes
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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Fox, Kevin M
-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 to our Copyright header

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Tim Schnell
On 11/27/13 4:12 PM, Steve Baker sba...@redhat.com 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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread 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: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-27 Thread Thomas Spatzier
Zane Bitter zbit...@redhat.com wrote on 27.11.2013 22:56:16: From: Zane Bitter zbit...@redhat.com 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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Ladislav Smola
:47 PM To: openstack-dev@lists.openstack.org mailto:openstack-dev@lists.openstack.org 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/2013 03:26 PM, Keith Bray wrote: On 11/25

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Steven Hardy
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 their own

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Zane Bitter
On 26/11/13 03:26, Keith Bray wrote: On 11/25/13 5:46 PM, Clint Byrum cl...@fewbar.com 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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Tim Schnell
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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Christopher Armstrong
On Tue, Nov 26, 2013 at 3:24 PM, Tim Schnell tim.schn...@rackspace.comwrote: 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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Steve Baker
On 11/27/2013 11:02 AM, Christopher Armstrong wrote: On Tue, Nov 26, 2013 at 3:24 PM, Tim Schnell tim.schn...@rackspace.com mailto:tim.schn...@rackspace.com wrote: Use Case #3 Grouping parameters would help the client make smarter decisions about how to display the

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Tim Schnell
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org openstack-dev@lists.openstack.orgmailto: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 tim.schn

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Christopher Armstrong
To: 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 tim.schn...@rackspace.com wrote: So the originally question

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Tim Schnell
On 11/26/13 4:16 PM, Steve Baker sba...@redhat.com 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,

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Tim Schnell
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Tuesday, November 26, 2013 4:02 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [heat][horizon]Heat UI related

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Angus Salkeld
: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap On Tue, Nov 26, 2013 at 3:24 PM, Tim Schnell tim.schn...@rackspace.commailto:tim.schn...@rackspace.com wrote: So the originally question that I attempted to pose was, Can we add a schema-less metadata section to the template

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Tim Schnell
@lists.openstack.orgmailto: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 tim.schn...@rackspace.commailto:tim.schn...@rackspace.com wrote: So the originally question that I attempted to pose was, Can

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Clint Byrum
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 that

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-26 Thread Clint Byrum
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 portable

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-25 Thread Tim Schnell
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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-25 Thread Clint Byrum
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 requirements

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-25 Thread Fox, Kevin M
...@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 UI developers driving the requirements behind

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-25 Thread Keith Bray
On 11/25/13 5:46 PM, Clint Byrum cl...@fewbar.com 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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-25 Thread Steve Baker
On 11/26/2013 03:26 PM, Keith Bray wrote: On 11/25/13 5:46 PM, Clint Byrum cl...@fewbar.com 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

Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap

2013-11-25 Thread Keith Bray
@lists.openstack.org Subject: Re: [openstack-dev] [heat][horizon]Heat UI related requirements roadmap On 11/26/2013 03:26 PM, Keith Bray wrote: On 11/25/13 5:46 PM, Clint Byrum cl...@fewbar.commailto:cl...@fewbar.com wrote: Excerpts from Tim Schnell's message of 2013-11-25 14:51:39 -0800: Hi