Orchestration service quotas
Stacks in OpenStack are managed by Heat. As we will see in the next section, the orchestration component in OpenStack enables assembling different resources to run a complete stack from code. This is an ideal use case for DevOps to provision resources in no time and leverage testing code and application functionality from one template file. On the other hand, controlling stacks for users can be more challenging as resources can be more demanded and rapidly exhausted. Heat also exposes quotas to control the number for stacks per tenant and resources per stack. Individual management of resources per stack in Heat is not straightforward. Increasing the limits, for example, of given resource quotas should be performed ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access