Hi all,

For the purpose of testing SoftwareConfig and SoftwareDeployments with Heat I started to build a custom Xenial image with Diskimage-builder. I followed this guide https://ask.openstack.org/en/question... (https://ask.openstack.org/en/question...) and ran disk-image-create like this:

diskimage-builder/bin/disk-image-create vm ubuntu os-collect-config os-refresh-config os-apply-config heat-config heat-config-script package-installs -t raw -o ubuntu-software-config.raw

When I tried to deploy my Heat stack applying software deployments, the deployment resources are stuck in "Create In Progress" state. I suppose that the stack is waiting for a signal via the Heat API notifying the service of success and this is not happening here.

This is the stack I test with: https://gist.github.com/mewald1/be31e...

I looked into the deployed machine and found out that the AUTH_URL in the [heat] section of os-collect-config.conf points to the internal URL of my Keystone service:

[DEFAULT]
command = os-refresh-config
collectors = ec2
collectors = heat
collectors = local

[heat]
auth_url = http://10.10.30.100:5000/v3/
user_id = a10a8bb5d98c49758ef672be40e37a60
password = e8624d4cd01748d599183eb7432c9c22
project_id = 24194fcc24264fcd8c2885093bdca553
stack_id = deploy-test/5423fe82-6457-4823-a958-259467efa3a5
resource_name = node

The address of 10.10.30.100 cannot be reached from an instance by design.

I want to understand two things:

1. How does the auth_url get into the instance?
2. Assuming it gets there by being injected by Heat in some way, how can I configure Heat to set the public URL?