Open Stack

On 26/10/12 14:16, Thierry Carrez wrote:
> Christopher B Ferris wrote:
>> Thanks for your thoughts. As for the EC2 v OpenStack APis, the EC2 API can be stripped out, leaving all functionality of nova
>> unimpaired. If the same could be true of the AWS Cloud Formation structures, it would make the project easier to consume
>> for those with persnickety legal departments.
>
> Indeed, Heat would basically be the first OpenStack project to adopt a
> third-party API as its main API (rather than introducing an
> OpenStack-specific API that lets us in control of the features we can
> expose).

I'm pleased to report that this is no longer correct - Heat now has an 
OpenStack-native API, and we intend to switch over to this as the main 
API in the very short term (i.e. the next month or two). Announcement 
here for those who missed it: 
https://lists.launchpad.net/openstack/msg17662.html

Christopher's objection seems to be to the template format, and it is 
indeed on of our goals to be able to launch as many existing 
CloudFormation templates as possible. He appears to believe that there 
could be some restriction on distributing the code because it is able to 
read data in a particular format. I must confess that I do not 
understand this objection at all.

cheers,
Zane.