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
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
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
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&
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?&
On Tue, Nov 26, 2013 at 4:35 PM, Tim Schnell
mailto:tim.schn...@rackspace.com>> wrote:
From: Christopher Armstrong
mailto:chris.armstr...@rackspace.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.opensta
On 11/26/13 5:24 PM, "Angus Salkeld" wrote:
>On 26/11/13 22:55 +, Tim Schnell wrote:
>>
>>On Tue, Nov 26, 2013 at 4:35 PM, Tim Schnell
>>mailto:tim.schn...@rackspace.com>> wrote:
>>
>>From: Christopher Armstrong
>>mailto:chris.armstr..
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)"
>> ,
>
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 al
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 Ca
hem
directly to Heat's database?
Tim Schnell
Software Developer
Rackspace
On 11/27/13 10:53 AM, "Thomas Spatzier" wrote:
>Thanks, that clarified the use case a bit. Bot looking at the use case
>now,
>isn't this stack tagging instead of template tagging?
>I.e. as
that isn't necessarily a part of any
catalog, in Horizon you can provide a template in a direct input text area
or via file upload.
Tim
>
>Thanks,
>Kevin
>
>
>From: Tim Schnell [tim.schn...@rackspace.com]
>Sent: Wednesday, November 27,
_
Thanks, that clarified the use case a bit. Bot looking at the use case now,
isn't this stack tagging instead of template tagging?
I.e. assume that for each stack a user creates, he/she can assign one or
more tags so you can do better queries to find stacks later?
Regard
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 va
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.
>>
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
Hi Heaters,
We would like to start a dialog on the general direction of the proposed Heater
project:
blueprint: https://blueprints.launchpad.net/heat/+spec/heat-template-repo
wiki: https://wiki.openstack.org/wiki/Heat/htr
It is important to us to start the discussion early but please note that t
On 12/5/13 11:33 AM, "Randall Burt" wrote:
>On Dec 5, 2013, at 11:10 AM, Clint Byrum
> wrote:
>
>> Excerpts from James Slagle's message of 2013-12-05 08:35:12 -0800:
>>> On Thu, Dec 5, 2013 at 11:10 AM, Clint Byrum wrote:
Excerpts from Monty Taylor's message of 2013-12-04 17:54:45 -0800:
On 12/5/13 12:17 PM, "Clint Byrum" wrote:
>Excerpts from Tim Schnell's message of 2013-12-05 09:49:03 -0800:
>>
>> On 12/5/13 11:33 AM, "Randall Burt" wrote:
>>
>> >On Dec 5, 2013, at 11:10 AM, Clint Byrum
>> > wrote:
>> >
>> >> Excerpts from James Slagle's message of 2013-12-05 08:35:12 -08
The original intention was to propose the Heater functionality as part of Heat.
I would just like to clarify that having Heater as a separate project is not
because of the impact of the gerrit reviews. The proposal for a separate Core
team or sub-project team was to solve the impact on reviews.
To resolve this thread, I have created 5 blueprints based on this mailing
list discussion. I have attempted to distill the proposed specification
down to what seemed generally agreed upon but if you feel strongly that I
have incorrectly captured something let's talk about it!
Here are the blueprin
On 12/6/13 4:32 PM, "Randall Burt" wrote:
>I hope I'm not re-opening worm cans here, and that's not my intent, but I
>just wanted to get a little clarification in-line below:
>
>On Dec 6, 2013, at 3:24 PM, Tim Schnell
> wrote:
>
>> To resolve this
On 12/23/13 5:02 AM, "Thomas Goirand" wrote:
>On 12/20/2013 04:39 PM, Matthias Runge wrote:
>> On 12/19/2013 04:45 PM, Thomas Goirand wrote:
>>> Hi,
>>>
>>> Sid has Django 1.6. Is it planned to add support for it? I currently
>>> don't know what to do with the Horizon package, as it's currently
On 1/15/14 9:01 AM, "Liz Blanchard" wrote:
>
>On Jan 9, 2014, at 4:41 AM, Jay Lau wrote:
>
>
>My bad, the image cannot be viewed.
>
>
>Upload again.
>
>
>
>Thanks,
>
>
>Jay
>
>
>
>2014/1/9 Jay Lau
>
>Hi,
>
>
>Now when using OpenStack dashboard to launch a stack, we need to first
>import the te
On 1/15/14 10:05 AM, "Jay Lau" wrote:
>Thanks Tim and Liz, comments in line.
>
>
>
>2014/1/15 Tim Schnell
>
>On 1/15/14 9:01 AM, "Liz Blanchard" wrote:
>
>
>>
>>On Jan 9, 2014, at 4:41 AM, Jay Lau wrote:
>>
>>
>&g
ture of nested stacks in the
>call. Tim Schnell brought this up as well and may be interested in
>helping define the use case and spec.
>
>On May 14, 2014, at 4:32 PM, Nilakhya Chatterjee
> wrote:
>
>> Hi All,
>>
>> I recently tried to create a nested stack wit
On 5/19/14 12:35 PM, "Randall Burt" wrote:
>On May 19, 2014, at 11:39 AM, Steven Hardy
> wrote:
>
>> On Mon, May 19, 2014 at 03:26:22PM +, Tim Schnell wrote:
>>> Hi Nilakhya,
>>>
>>> As Randall mentioned we did discuss this exact iss
Blueprint:
https://blueprints.launchpad.net/heat/+spec/explode-nested-resources
Spec: https://wiki.openstack.org/wiki/Heat/explode-resource-list
Tim
On 5/19/14 1:53 PM, "Tim Schnell" wrote:
>On 5/19/14 12:35 PM, "Randall Burt" wrote:
>
>
>>On May
Hi Edgar,
It seems like this blueprint is related more to building an api that
manages a network topology more than one that needs to build out the
dependencies between resources to help create the network topology. If we
are talking about just an api to "save", "duplicate", and "share" these
netw
Hey everyone,
Just a quick demo of the Resource Topology. I'm working on getting it into Code
Review for Horizon either today or tomorrow.
http://www.youtube.com/watch?v=pe9EM8WhLPA
Thanks!
[cid:F8A7CDE7-7AE1-42CB-A834-D228A925FF7A]
<>___
OpenStack-dev
-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Heat] [Horizon] Heat Resource Topology Demo
On 07/10/2013 04:59 AM, Tim Schnell wrote:
Just a quick demo of the Resource Topology. I'm working on getting it into Code
Review for Horizon either today or tomorrow.
http://www.youtube.com/wa
Most of my navigation related issues can be summed up into 3 problems.
1. Not having a secondary level of navigation in the left-nav really
restricts the level of granularity that can be achieved through the navigation.
Having an accordion-like nav structure would help this as well as setting
Hey Liz,
I briefly brought up horizontal navigation in the IRC meeting last week. I
agree, first of all, that Left Nav will run into scaling issues at some point
but I think Gabriel Hurley made a good point in that doing something as drastic
as getting rid of the Left Nav and replacing it with
33 matches
Mail list logo
