<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 07/04/15 10:09, Fox, Kevin M wrote:<br>
    </div>
    <blockquote
      cite="mid:1A3C52DFCD06494D8528644858247BF01A1CF489@EX10MBOX03.pnnl.gov"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Exchange Server">
      <!-- converted from text -->
      <style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
      <div>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.<br>
        <br>
      </div>
    </blockquote>
    <br>
    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). <br>
    <blockquote
      cite="mid:1A3C52DFCD06494D8528644858247BF01A1CF489@EX10MBOX03.pnnl.gov"
      type="cite">
      <div><strong>
          <div><font color="#000000" face="Tahoma" size="2"> </font></div>
        </strong>
        <hr tabindex="-1">
        <font face="Tahoma" size="2"><b>From:</b> Steve Baker<br>
          <b>Sent:</b> Monday, April 06, 2015 2:36:07 PM<br>
          <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
          <b>Subject:</b> Re: [openstack-dev] [Heat][Horizon] What we
          can do for Heat in Horizon else?<br>
        </font><br>
      </div>
      <font size="2"><span style="font-size:10pt;">
          <div class="PlainText">On 02/04/15 21:55, Sergey Kraynev
            wrote:<br>
            > Hi community.<br>
            ><br>
            > I want to ask feedback from our Heat team and also
            involve Horizon <br>
            > team in this discussion.<br>
            > AFAIK during Kilo was implemented bp:<br>
            > <a moz-do-not-send="true"
href="https://blueprints.launchpad.net/horizon/+spec/heat-ui-improvement">https://blueprints.launchpad.net/horizon/+spec/heat-ui-improvement</a><br>
            ><br>
            > This bp add more base Heat functionality to Horizon.<br>
            > I asked some ideas from Heat guys. What we want to have
            here else ?<br>
            ><br>
            > There is only one idea for me about topology:<br>
            > create some filters for displaying only particular
            resources (by their <br>
            > type)<br>
            > F.e. stack has 50 resources, but there is half of them
            network resources.<br>
            > As user I want to see only network level, so I enable
            filtering by <br>
            > network resources.<br>
            ><br>
            ><br>
            ><br>
            Horizon can't launch stacks when the templates do file
            inclusion via <br>
            get_file or type inclusion. There was an effort a while ago
            to build a <br>
            stack-create workflow which introspected the template/env
            and prompted <br>
            for the required files but it wasn't completed.<br>
            <br>
            Something I want to discuss in Vancouver is whether we
            should consider <br>
            supporting an archive format for packaging
            templates/environments/files <br>
            into a single file. The REST API would *not* support this
            archive format <br>
            so it would be up to the "client" (horizon server or heat
            CLI) to unpack <br>
            the archive before calling stack-create.<br>
            <br>
            Something which solves multi-file horizon stack-create would
            be my No.1 <br>
            feature request.<br>
            <br>
__________________________________________________________________________<br>
            OpenStack Development Mailing List (not for usage questions)<br>
            Unsubscribe:
            <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
            <a moz-do-not-send="true"
              href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
          </div>
        </span></font>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>