Ask Your Question

Revision history [back]

Historically there have been two uses of the term 'orchestration' in the OpenStack community. I suspect that this may be at the root of your question.

The first (and wrong ;) use of the term was to describe a way to organise the internal state of the Nova API to keep track of the various external things it has to co-ordinate in order to start an instance - nova-compute, cinder, neutron, &c. This is not what Heat is doing.

Heat's purpose is to orchestrate the end-user's application: it allows you to provide a declarative model of the desired topology, and then infers the dependencies and makes all of the API calls necessary to make it a reality (as well as keeping track of errors, allowing updates to the model, and so on).