: 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
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
, 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
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
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
-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
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
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
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
)
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
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
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
)
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
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
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
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
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
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
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
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.
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:
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
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
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
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
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
-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
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
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,
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
: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
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
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
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
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
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
@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
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
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,
@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
: [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
@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
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
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
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
...@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
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
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
@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
49 matches
Mail list logo
