[openstack-dev] [Heat][Horizon] Liberty horizon and get_file workaround?

Lin Hua Cheng os.lcheng at gmail.com
Fri Apr 22 19:42:13 UTC 2016


Based from stable policy, we don't backport new features [1]. The new
feature also reads from an external URL, which I think might be too risky
to add to stable branches.

-Lin

[1]
http://docs.openstack.org/project-team-guide/stable-branches.html#review-guidelines

On Fri, Apr 22, 2016 at 3:14 AM, Ethan Lynn <xuanlangjian at gmail.com> wrote:

> There’s a patch to fix this problem in mitaka
> https://review.openstack.org/#/c/241700/ , Need to here more feedbacks
> about backport it to liberty release
> https://review.openstack.org/#/c/260436/ .
>
>
> Best Regards,
> Ethan Lynn
> xuanlangjian at gmail.com
>
>
>
>
> On Apr 22, 2016, at 13:06, Jason Pascucci <jrp at juniper.net> wrote:
>
> Hi,
>
> I wanted to add my yaml as new resources (via
> /etc/heat/environment.d/default.yaml, but we use some external files in the
> OS::Nova::Server personality section.
>
> It looks like the heat cli handles that when you pass yaml to it, but I
> couldn’t get it to work either through horizon, or even heat-cli when it
> was a get_file from inside of the new resources.
>                 I can see why file:// might not work, but I sort of
> expected that at least http://blah would still work within horizon (if
> so, I could just stick it in swift somewhere, but alas, no soup).
>
> What’s the fastest path to a workaround?
>                 I was thinking of making a new resource plugin that reads
> the path, and returns the contents so it could be used as a get_attr,
> essentially cribbing the code from the heat command line processing.
>                 Is there a better/sane way?
>                 Is there some conceptual thing I’m missing that makes this
> moot?
>
> Thanks in advance,
>
> JRPascucci
> Juniper Networks
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160422/a963266d/attachment.html>


More information about the OpenStack-dev mailing list