Re: openstack / CF v234 deployment


Amit Kumar Gupta
 

Hi William,

Yes, this looks like a mixup between domain and system_domain. Both should
be the same value, system.domain.com. The two separate properties exist
for historical reasons, we plan to reduce back down to 1 to avoid these
confusions in the future.

Cheers,
Amit

On Fri, Apr 15, 2016 at 11:43 AM, Bean William R <BeanWilliamR(a)johndeere.com
wrote:
We've ventured through
https://docs.cloudfoundry.org/deploying/openstack/index.html and have CF
deployed on OpenStack.

[root(a)cfinstaller my-bosh]# bosh deployments
...

+------------------+--------------+------------------------------------------------+--------------+
| Name | Release(s) | Stemcell(s)
| Cloud Config |

+------------------+--------------+------------------------------------------------+--------------+
| cloudfoundry-lab | cf/234+dev.1 |
bosh-openstack-kvm-ubuntu-trusty-go_agent/3215 | none |

+------------------+--------------+------------------------------------------------+--------------+

After a bosh deploy, we are able to login with the admin credentials, and
cf push a staticfile app:


[root(a)cfinstaller billhello-project]# cf push billhello -m 64M
...
requested state: started
instances: 1/1
usage: 64M x 1 instances
urls: billhello.domain.com
last uploaded: Fri Apr 15 18:30:38 UTC 2016
stack: unknown
buildpack: staticfile 1.3.5

state since cpu memory disk
details
#0 running 2016-04-15 06:30:50 PM 0.0% 3.6M of 64M 5.4M of 1G


However we are not able to use the loggregator service from the cf-cli:

[root(a)cfinstaller billhello-project]# export CF_TRACE=true
[root(a)cfinstaller billhello-project]# cf logs billhello
...
WEBSOCKET REQUEST: [2016-04-15T18:35:22Z]
GET /tail/?app=d0a97a19-4794-4584-82ce-1b2fe596cf78 HTTP/1.1
Host: wss://loggregator.system.domain.com:4443
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Version: 13
Sec-WebSocket-Key: [HIDDEN]
Origin: http://localhost
Authorization: [PRIVATE DATA HIDDEN]


WEBSOCKET RESPONSE: [2016-04-15T18:35:22Z]
HTTP/1.1 404 Not Found
Content-Length: 91
Content-Type: text/plain; charset=utf-8
X-Cf-Routererror: unknown_route
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: c8a05edd-a6b9-48d0-6f05-1c0aaa76f45f
Date: Fri, 15 Apr 2016 18:35:23 GMT

FAILED
Error dialing loggregator server: websocket: bad handshake.
Please ask your Cloud Foundry Operator to check the platform configuration
(loggregator endpoint is wss://loggregator.system.cflab.deere.com:4443).


We've already tried just restarting the services on the
loggregator_trafficcontroller_z1/0 instance, and logging out & back in with
the cf-cli... neither helps.

How does this wss://loggregator.system.domain.com:4443 get added to
nats? From the loggregator_trafficcontroller_z1/0 instance, the only
routes in /var/vcap/jobs/route_registrar/config/registrar_settings.yml are:

routes:
[{"name":"doppler","port":8081,"registration_interval":"20s","uris":["
doppler.domain.com
"]},{"name":"loggregator","port":8080,"registration_interval":"20s","uris":["
loggregator.domain.com"]}]

Should there be one for loggregator.system.domain.com? Is this just a
mismatch between system_domain and domain? Any troubleshooting tips?

Thanks,
William Bean

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.