Excerpts from Steve Baker's message on 26.11.2013 23:29:06: > From: Steve Baker <sba...@redhat.com> > To: openstack-dev@lists.openstack.org, > Date: 26.11.2013 23:32 > 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 <tim.schn...@rackspace.com > > wrote:
<snip> > Good point, I'd like to revise my previous parameter-groups example: > parameter-groups: > - name: db > description: Database configuration options > parameters: [db_name, db_username, db_password] > - name: web_node > description: Web server configuration > parameters: [web_node_name, keypair] > parameters: > # as above, but without requiring any order or group attributes +1 on this approach. Very clean and gives you all the information you would need to the UI use case. And as you say, does not have any impact on the current way parameters are processed by Heat. > > Here, parameter-groups is a list which implies the order, and > parameters are specified in the group as a list, so we get the order > from that too. This means a new parameter-groups section which > contains anything required to build a good parameters form, and no > modifications required to the parameters section at all. > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
