Main heat engin in legacy mode

Solution Unverified - Updated -

Issue

  • A while ago I reported problem with Heat engine consuming excessive amount of memory while deploying overcloud stack.
  • This is now tracked in Red Hat bugzilla as 1626675.
  • And I also follow Heat OpenStack bug. So in one of the comments on https://review.openstack.org/386444 there is this sentence:
> Use RPC to retrieve nested stack output
>    Instead of loading the stack in memory, use RPC to get the stack and its
>   output. It releases memory pressure from the main engine in legacy mode.
  • So my question, what is "main engine in legacy mode" and what is not legacy mode?
  • And is there any way to switch heat-engine to not being legacy?

Environment

  • Red Hat OpenStack Platform 8

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content