What's the version of Heat can compatible with Openstack-Folsom?

The final grizzly release should work fine with Folsom. Can you be more specific about the issue you're seeing?

Tested with 2013.1 release in Folsom:

[root@Staging-I heat]# ./install.sh
NOT replacing existing config file /etc/bash_completion.d/heat-cfn
NOT replacing existing config file /etc/boto.cfg
Installing heat-api-cfn.conf in /etc/heat
Installing heat-api-cfn-paste.ini in /etc/heat
Installing heat-api-cloudwatch.conf in /etc/heat
Installing heat-api-cloudwatch-paste.ini in /etc/heat
Installing heat-api.conf in /etc/heat
Installing heat-api-paste.ini in /etc/heat
Installing heat-engine.conf in /etc/heat
Installing policy.json in /etc/heat

The Heat install process is stopping in 'Installing policy.json in /etc/heat', install failed.

I can install V7.release successfully in the same Folsom-environment.
So I guess maybe 2013.1 release is not compatible with Folsom.

OK, so the output of install.sh is redirected to /dev/null:

https://github.com/openstack/heat/blob/2013.1/install.sh#L77

I'm guessing at some point setup.py changed from printing to stderr to stdout. That's why you're not seeing any output. It doesn't necessarily mean that Heat is not installed. If you have checked and Heat really is not installed, then remove the "> /dev/null" from the install.sh script and look for errors in the output.

Even the trunk version of Heat installs just fine with OpenStack Folsom, though it may try to pull in updated client libraries. Compatibility with Folsom was an explicit design goal of the grizzly release.

Hi Zane, thanks very much for your kindly help. It is clear to me now.