[openstack-dev] [heat] computed package names?

Mike Spreitzer mspreitz at us.ibm.com
Tue Apr 15 19:57:36 UTC 2014


Zane Bitter <zbitter at redhat.com> wrote on 04/15/2014 03:29:03 PM:

> On 15/04/14 14:31, Mike Spreitzer wrote:
> > It appears that in Fedora 19 and 20 the Wordpress examples need to
> > install different packages than in every other release (see my 
debugging
> > in https://review.openstack.org/#/c/87065/).  I just got a complaint
> > from Heat validation that I can't do this:
> >
> >          "AWS::CloudFormation::Init" : {
> >            "config" : {
> >              "packages" : {
> >                "yum" : {
> > { "Fn::FindInMap" : [ "Pkgset2Pkgs", { "Fn::FindInMap" : [
> > "Distro2Pkgset", { "Ref" : "LinuxDistribution" }, "db" ] }, "client" ] 
}
> > : [],
> > { "Fn::FindInMap" : [ "Pkgset2Pkgs", { "Fn::FindInMap" : [
> > "Distro2Pkgset", { "Ref" : "LinuxDistribution" }, "db" ] }, "server" ] 
}
> > : [],
> >
> 
> .. in 
> JSON a property name cannot be an object ...

Ah, right.  So what would be the simplest way to enable this use case? 
Perhaps a generalization of AWS::CloudFormation::Init that allows the 
package names to be objects (that evaluate to strings, of course)?  Maybe 
allow, e.g., "yum" to be associated with not a map but rather a list of 
pairs (2-element lists)?

Thanks,
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140415/593b56ab/attachment.html>


More information about the OpenStack-dev mailing list