Re: [openstack-dev] [Heat][Horizon] What we can do for Heat in Horizon else?

2015-04-06 Thread Steve Baker

On 07/04/15 10:09, Fox, Kevin M wrote:
Would that be better done as part of the glance artifact work? You 
could upload multiple files as an artifact, then launch the templates 
from the artifact. May need some of the same ui bits, but not specific 
to heat.




That would be good too, but it would still be desirable for a user to 
launch a template from a local file, even when it references other local 
files (without having to go through an artifact repository).

*
*

*From:* Steve Baker
*Sent:* Monday, April 06, 2015 2:36:07 PM
*To:* openstack-dev@lists.openstack.org
*Subject:* Re: [openstack-dev] [Heat][Horizon] What we can do for Heat 
in Horizon else?


On 02/04/15 21:55, Sergey Kraynev wrote:
> Hi community.
>
> I want to ask feedback from our Heat team and also involve Horizon
> team in this discussion.
> AFAIK during Kilo was implemented bp:
> https://blueprints.launchpad.net/horizon/+spec/heat-ui-improvement
>
> This bp add more base Heat functionality to Horizon.
> I asked some ideas from Heat guys. What we want to have here else ?
>
> There is only one idea for me about topology:
> create some filters for displaying only particular resources (by their
> type)
> F.e. stack has 50 resources, but there is half of them network 
resources.

> As user I want to see only network level, so I enable filtering by
> network resources.
>
>
>
Horizon can't launch stacks when the templates do file inclusion via
get_file or type inclusion. There was an effort a while ago to build a
stack-create workflow which introspected the template/env and prompted
for the required files but it wasn't completed.

Something I want to discuss in Vancouver is whether we should consider
supporting an archive format for packaging templates/environments/files
into a single file. The REST API would *not* support this archive format
so it would be up to the "client" (horizon server or heat CLI) to unpack
the archive before calling stack-create.

Something which solves multi-file horizon stack-create would be my No.1
feature request.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Heat][Horizon] What we can do for Heat in Horizon else?

2015-04-06 Thread Fox, Kevin M
Would that be better done as part of the glance artifact work? You could upload 
multiple files as an artifact, then launch the templates from the artifact. May 
need some of the same ui bits, but not specific to heat.

Thanks,
Kevin


From: Steve Baker
Sent: Monday, April 06, 2015 2:36:07 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Heat][Horizon] What we can do for Heat in Horizon 
else?

On 02/04/15 21:55, Sergey Kraynev wrote:
> Hi community.
>
> I want to ask feedback from our Heat team and also involve Horizon
> team in this discussion.
> AFAIK during Kilo was implemented bp:
> https://blueprints.launchpad.net/horizon/+spec/heat-ui-improvement
>
> This bp add more base Heat functionality to Horizon.
> I asked some ideas from Heat guys. What we want to have here else ?
>
> There is only one idea for me about topology:
> create some filters for displaying only particular resources (by their
> type)
> F.e. stack has 50 resources, but there is half of them network resources.
> As user I want to see only network level, so I enable filtering by
> network resources.
>
>
>
Horizon can't launch stacks when the templates do file inclusion via
get_file or type inclusion. There was an effort a while ago to build a
stack-create workflow which introspected the template/env and prompted
for the required files but it wasn't completed.

Something I want to discuss in Vancouver is whether we should consider
supporting an archive format for packaging templates/environments/files
into a single file. The REST API would *not* support this archive format
so it would be up to the "client" (horizon server or heat CLI) to unpack
the archive before calling stack-create.

Something which solves multi-file horizon stack-create would be my No.1
feature request.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Heat][Horizon] What we can do for Heat in Horizon else?

2015-04-06 Thread Steve Baker

On 02/04/15 21:55, Sergey Kraynev wrote:

Hi community.

I want to ask feedback from our Heat team and also involve Horizon 
team in this discussion.

AFAIK during Kilo was implemented bp:
https://blueprints.launchpad.net/horizon/+spec/heat-ui-improvement

This bp add more base Heat functionality to Horizon.
I asked some ideas from Heat guys. What we want to have here else ?

There is only one idea for me about topology:
create some filters for displaying only particular resources (by their 
type)

F.e. stack has 50 resources, but there is half of them network resources.
As user I want to see only network level, so I enable filtering by 
network resources.




Horizon can't launch stacks when the templates do file inclusion via 
get_file or type inclusion. There was an effort a while ago to build a 
stack-create workflow which introspected the template/env and prompted 
for the required files but it wasn't completed.


Something I want to discuss in Vancouver is whether we should consider 
supporting an archive format for packaging templates/environments/files 
into a single file. The REST API would *not* support this archive format 
so it would be up to the "client" (horizon server or heat CLI) to unpack 
the archive before calling stack-create.


Something which solves multi-file horizon stack-create would be my No.1 
feature request.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Heat][Horizon] What we can do for Heat in Horizon else?

2015-04-02 Thread Fox, Kevin M
+1. I have to copy/paste in nested stack uuids all the time. :/

Thanks,
Kevin


From: Pavlo Shchelokovskyy
Sent: Thursday, April 02, 2015 3:05:14 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Heat][Horizon] What we can do for Heat in Horizon 
else?

Hi folks,

there is another not covered feature that jumps at me:

say you have a stack containing an autoscaling group (a nested stack) where the 
scaled resource is also a nested stack. I can click on the uuid of the asg to 
get a page similar to other stacks showing me the structure of the nested stack 
described by autoscaling group, but I can not further click on the uuid of the 
scaled resource to get its representation as a stack. Copy-pasting the uuid of 
the scaled resource into the Horizon url as /project/stacks/ 
does the trick and the structure of the resource as a stack is displayed.

As an example you can use the templates for the test_autoscaling_lb integration 
test, under review [1]
[1] https://review.openstack.org/#/c/165944/

Best regards,

Pavlo Shchelokovskyy
Software Engineer
Mirantis Inc
www.mirantis.com<http://www.mirantis.com>

On Thu, Apr 2, 2015 at 11:55 AM, Sergey Kraynev 
mailto:skray...@mirantis.com>> wrote:
Hi community.

I want to ask feedback from our Heat team and also involve Horizon team in this 
discussion.
AFAIK during Kilo was implemented bp:
https://blueprints.launchpad.net/horizon/+spec/heat-ui-improvement

This bp add more base Heat functionality to Horizon.
I asked some ideas from Heat guys. What we want to have here else ?

There is only one idea for me about topology:
create some filters for displaying only particular resources (by their type)
F.e. stack has 50 resources, but there is half of them network resources.
As user I want to see only network level, so I enable filtering by network 
resources.


Regards,
Sergey.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Heat][Horizon] What we can do for Heat in Horizon else?

2015-04-02 Thread Pavlo Shchelokovskyy
Hi folks,

there is another not covered feature that jumps at me:

say you have a stack containing an autoscaling group (a nested stack) where
the scaled resource is also a nested stack. I can click on the uuid of the
asg to get a page similar to other stacks showing me the structure of the
nested stack described by autoscaling group, but I can not further click on
the uuid of the scaled resource to get its representation as a stack.
Copy-pasting the uuid of the scaled resource into the Horizon url as
/project/stacks/ does the trick and the structure of the
resource as a stack is displayed.

As an example you can use the templates for the test_autoscaling_lb
integration test, under review [1]
[1] https://review.openstack.org/#/c/165944/

Best regards,

Pavlo Shchelokovskyy
Software Engineer
Mirantis Inc
www.mirantis.com

On Thu, Apr 2, 2015 at 11:55 AM, Sergey Kraynev 
wrote:

> Hi community.
>
> I want to ask feedback from our Heat team and also involve Horizon team in
> this discussion.
> AFAIK during Kilo was implemented bp:
> https://blueprints.launchpad.net/horizon/+spec/heat-ui-improvement
>
> This bp add more base Heat functionality to Horizon.
> I asked some ideas from Heat guys. What we want to have here else ?
>
> There is only one idea for me about topology:
> create some filters for displaying only particular resources (by their
> type)
> F.e. stack has 50 resources, but there is half of them network resources.
> As user I want to see only network level, so I enable filtering by network
> resources.
>
>
> Regards,
> Sergey.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Heat][Horizon] What we can do for Heat in Horizon else?

2015-04-02 Thread Sergey Kraynev
Hi community.

I want to ask feedback from our Heat team and also involve Horizon team in
this discussion.
AFAIK during Kilo was implemented bp:
https://blueprints.launchpad.net/horizon/+spec/heat-ui-improvement

This bp add more base Heat functionality to Horizon.
I asked some ideas from Heat guys. What we want to have here else ?

There is only one idea for me about topology:
create some filters for displaying only particular resources (by their type)
F.e. stack has 50 resources, but there is half of them network resources.
As user I want to see only network level, so I enable filtering by network
resources.


Regards,
Sergey.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev