Zane Bitter <zbit...@redhat.com> wrote on 04/02/2014 05:36:43 PM: > I think that if you're going to propose a new feature, you should at > least give us a clue who you think is going to use it and what for ;)
I was not eager to do that yet because I have not found a fully satisfactory answer yet, at this point I am exploring options. But the problem I am thinking about is how Heat might connect to a holistic scheduler (a scheduler that makes a joint decision about a bunch of resources of various types). Such a scheduler needs input describing the things to be scheduled and the policies to apply in scheduling; the first half of that sounds a lot like a Heat template, so my thoughts go in that direction. But the HOT language today (since https://review.openstack.org/#/c/83758/ was merged) does not have a place to put policy that is not specific to a single resource. > IIRC this has been discussed in the past and the justifications for > including it in the template (as opposed to allowing metadata to be > attached in the ReST API, as other projects already do for many things) > were not compelling. I see that Keith Bray mentioned https://wiki.openstack.org/wiki/Heat/StackMetadata and https://wiki.openstack.org/wiki/Heat/UI in another reply on this thread. Are there additional places to look to find that discussion? I have also heard that there has been discussion of language extension issues. Is that a separate discussion and, if so, where can I read it? Thanks, Mike
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev