[openstack-dev] [OpenStack][HEAT][Dashboard] Edit JSON tempalte on OpenStack Dashboard
Jay Lau
jay.lau.513 at gmail.com
Wed Jan 15 16:05:55 UTC 2014
Thanks Tim and Liz, comments in line.
2014/1/15 Tim Schnell <tim.schnell at rackspace.com>
> On 1/15/14 9:01 AM, "Liz Blanchard" <lsurette at redhat.com> wrote:
>
>
> >
> >On Jan 9, 2014, at 4:41 AM, Jay Lau <jay.lau.513 at gmail.com> wrote:
> >
> >
> >My bad, the image cannot be viewed.
> >
> >
> >Upload again.
> >
> >
> >
> >Thanks,
> >
> >
> >Jay
> >
> >
> >
> >2014/1/9 Jay Lau <jay.lau.513 at gmail.com>
> >
> >Hi,
> >
> >
> >Now when using OpenStack dashboard to launch a stack, we need to first
> >import the template then create the stack, but there is no way to enable
> >admin to view/modify the template.
>
> Hi Jay,
>
> Sorry I meant to respond to this a few days ago. Currently, in the
> dashboard you have the ability to copy/paste a template into a text area
> and then edit it before you attempt the stack-create. This seems to solve
> the use case that you have mentioned although I agree that there is room
> for improvement in the user experience.
>
> The reason I bring up the distinction is because the template that you
> reference below has a much broader scope. It includes storing and managing
> templates for future use. If you are intending to add all of this
> functionality into the Dashboard then I would suggest waiting for a
> template storage solution to get done. There is currently a blueprint and
> discussion happening in Glance to take on this ability and then I would
> imagine that the Dashboard can consume it.
>
> see:
> https://blueprints.launchpad.net/glance/+spec/metadata-artifact-repository
>
> If you are intending to simply add an additional page for editing the
> template if the user chooses to retrieve it via the URL option then my
> only suggestion would be to have a flag that gets stored in the session
> that allows the user to bypass the editing step for launching templates
> since some users will never need to edit templates.
>
@Tim, I think that it might be ok to enable admin still be able to see the
overall JSON/YAML template by the edit page even if s/he does not want to
edit it. ;-)
I'm planning to add both edit/create page to heat, and I noticed that AWS
already have such feature:
http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-using-cloudformer.html,
I'm now trying if we can leverage some from it.
So I think that the dashboard should probably add a new button named as
create. Yes, now we cannot store template, so my thinking is that once
admin create template finished, then s/he can simply export it and save it
locally for future use.
>
> >
> >
> >What about add a new page between import template and launch stack to
> >give admin an opportunity to edit the template?
> >
> >
> >I noticed that we already have a blueprint tracing this:
> >https://blueprints.launchpad.net/horizon/+spec/heat-template-management
> ><https://blueprints.launchpad.net/horizon/+spec/heat-template-management>
> >
> >
> >
> >I did some investigation, seems we can leverage
> >http://jsoneditoronline.org/ <http://jsoneditoronline.org/> to enable
> >OpenStack dashboard have this ability (Only for JSON template).
> >
> >
> >
> >Hi Jay,
> >
> >
> >I really like the idea of allowing users to edit these templates easily
> >right through the dashboard. Are all template files in JSON? I would say
> >we should try to find a solution to add to the dashboard that would
> >support all (or as many as possible) formats
> > of template that we can.
>
> I agree with Liz here, templates can be in JSON or YAML format so if we do
> add a javascript library to provide syntax highlighting and things then I
> would want it to work with YAML as well as JSON.
>
> -Tim
>
> >
> >
> >Best,
> >Liz
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >Thanks,
> >
> >
> >Jay
> >
> >
> >
> >
> >
> >
> ><json.png>_______________________________________________
> >OpenStack-dev mailing list
> >OpenStack-dev at lists.openstack.org
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> >
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> 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/20140116/f1466c9b/attachment.html>
More information about the OpenStack-dev
mailing list