heat::keystone::domain only works if heat & keystone on the same box

[Matt Fischer]

The code in heat::keystone::domain assumes that keystone and heat are on the same server. If keystone is on a separate box and you include this file, it fails in the heat_config section. This section should be moved into a different location. Unfortunately I don't know a great way to separate these that doesn't involve duplicated variables.

One no so great work around is to set all the manage_ stuff in this file to false and then do the resource managing in your own manifests. That's what we're doing for now.

The issue is similar to https://bugs.launchpad.net/puppet-heat/+bug/1393293

[Emilien Macchi (emilienm)]

note: we're doing the same workaround in tripleo now too.

[Emilien Macchi (emilienm)]

This bug was last updated over 180 days ago, as tripleo is a fast moving project and we'd like to get the tracker down to currently actionable bugs, this is getting marked as Invalid. If the issue still exists, please feel free to reopen it.

[Takashi Kajinami (kajinamit)]

Now you can deploy heat and keystone in completely different nodes by creating the /etc/openstack/puppet/admin-clouds.yaml file in both nodes.
This is created automatically by keystone::bootstrap in keystone nodes but you can create the same as an extra resource in heat nodes.