BOSH Openstack Solo deployment timeout errors in compile phase.

[Bill Chapman]

I"m trying to deploy CF 200 with the following Setup. 

Stemcell: 2922

MicroBOSH with https://gist.github.com/byllc/5220c7bb6f8b4f6ad1aa

BOSH with Openstack solo manifest https://gist.github.com/byllc/aeb96e29119e5e908a98

CF with manifest https://gist.github.com/byllc/6c7bf489f7c8fd7a64d0

The BOSH is the latest master branch with a monitor plugin I am working on and it deploys successfully. 

I am getting timeouts waiting for the agent to come alive while deploying CF: 

Timed out pinging to 99521135-0eb4-44cc-85f0-8681efa34de3 after 600 seconds (00:14:02)

I've been through several posts on here already but have not yet found the issue

https://groups.google.com/a/cloudfoundry.org/forum/#!topic/bosh-users/I2Ttz8e3zGs

Logging in to a node before BOSH cleans it up yields:

2015-04-18_00:35:22.79157 [settingsService] 2015/04/18 00:35:22 ERROR - Failed loading settings via fetcher: Getting settings from url: Get http://127.0.0.1:25777/instances/vm-ef46f898-e951-4766-ad5c-9d30a72ce17e/settings: dial tcp 127.0.0.1:25777: connection refused
2015-04-18_00:35:22.79169 [File System] 2015/04/18 00:35:22 DEBUG - Reading file /var/vcap/bosh/settings.json
2015-04-18_00:35:22.79180 [settingsService] 2015/04/18 00:35:22 ERROR - Failed reading settings from file Opening file /var/vcap/bosh/settings.json: open /var/vcap/bosh/settings.json: no such file or directory
2015-04-18_00:35:22.79189 [main] 2015/04/18 00:35:22 ERROR - App setup Running bootstrap: Fetching settings: Invoking settings fetcher: Getting settings from url: Get http://127.0.0.1:25777/instances/vm-ef46f898-e951-4766-ad5c-9d30a72ce17e/settings: dial tcp 127.0.0.1:25777: connection refused

I'm guessing this is a problem with the Bosh Solo configuration because it is trying to access settings from localhost when it should be hitting the director VM?  But changing the ip address in the bosh-openstack-solo.yml to use the floating ip instead of localhost seems a bit aggressive and potentially problematic.  Can anyone see something else that I'm missing? 

Thanks.  

[Bill Chapman]

OK,  It looks like the problem was the 127.0.0.1 in the manifest. It appears that changing that to the internal or floating ip of the  "core" vm gets by that error.   So for now I think the problem is fixed.   

My question now is whether that openstack-solo manifest could work at all with 127.0.0.1 as the ip for each component?