Sergey, What do you think about adoption of/integration with other types of resource definition languages used in OpenStack, for example, Heat Orchestration Templates?
-- Best regards, Oleg Gelbukh On Thu, Feb 27, 2014 at 6:31 PM, Sergey Skripnick <sskripn...@mirantis.com>wrote: > > Hello, > > Problem: what about deployment specific parts >> Template string in config? %imageid% or similar? >> Image name regex, rather than image name? so can work with multiple >> deployments, eg ^cirros$ >> > > > so we have a few solutions for today: function, vars, and "special args". > > > FUNCTION > ======== > args: {"image_id": {"$func": "img_by_reg", "$args": ["ubuntu.*"]}} > > Flexible but configuration looks complex. > > VARS > ==== > vars : { > $image1 : {"$func": "img_by_reg", "$args": ["ubuntu.*"]}, > $image2: {"$func": "img_by_reg", "$args": ["centos.*"]} > } > args: { > image_id: $image1, > alt_image_id: $image2 > } > > This may be an addition to the first solution, but personally to me it > looks like overkill. > > SPECIAL ARGS > ============ > args: {"image_re": {"ubuntu.*"}} > > Very simple configuration, but less flexible then others. IMO all three may > be implemented. > > I vote for "special args", and IMO functions may be implemented too. > Please feel free to propose other solutions. > > -- > Regards, > Sergey Skripnick > > _______________________________________________ > 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