We generally recommend to use a separate system domain from the shared apps domain. That could look like Our test environment for example uses a1.cf-app.com as the system domain and a1-app.cf-app.com

development. OK thanks so much for all the detailed info you've included here. I'll dig into it and will report back here for any questions or issues. Thanks! public documentation suffices for any

Thanks for the response Rohit. I hope this is the beginning of a good long discussion on the topic. :) Before going too deep with the '\' proposal are you aware if the loggregator team considered

I am looking for a way to push an application (ruby/node/java) and have a script run prior to the application starting that will setup SSHFS and move some of the content onto the share before the

OK that confirms what I thought. Thanks! Assk, any thoughts as well? Did that make sense to you? -- Jean-Sebastien

The cf-release templates allow for a "system_domain" ( https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L616), this allows for a separate namespace for non-app

We've seen issues on some environments where requests to cc that involve cc making a request to uaa or hm9k have a 5s delay while the local consul agent fails to resolves the DNS for uaa/hm9k, before

Hey Matt, I'm trying to think of other things that would affect only the endpoints that interact with UAA and would be fixed after a CC restart. I'm wondering if it's possible there are a large

What version of cf-release? If it's recent, see the "Important" section of the release notes about colocating the new route_registrar for v217

I'm pleased to announce the release of the java-buildpack, version 3.3. This release contains updates to various dependencies. - When processing Java Options the $ and \ characters are no longer

I filed a GitHub issue: https://github.com/cloudfoundry/cf-registrar/issues/7 What is happening was that - NATS receives route registration from CC and Traffic Controller - UAA not sending route

You can use your bosh director as a gateway: bosh ssh --gateway-host ADDRESS-OF-DIRECTOR --gateway-user vcap

You can proxy through the director or whatever else if you'd like with `bosh ssh --gateway_host director.example.com --gateway_user vcap --gateway_identity_file /path/to/bosh_directors_key`. BOSH

I was under the impression that you need to be able to connect directly, but I can't say that definitively. Perhaps someone else can confirm. Dan

Hi Daniel, 10.0.16.103 is the internal address of that particular VM within the VPC (I've deployed CF in AWS). So I can't access it directly. I thought that was the point of using "bosh ssh", i.e.,

Have you checked that the connection is not being blocked by a firewall? What happens if you SSH directly to that IP? Dan

Hi, I was trying "bosh ssh" in the interactive mode and after choosing the VM it hangs for a bit then times out. I was following this tutorial:

I only have one ETCD node, and it's the correct address in the metron config. From: Rohit Kumar <rokumar(a)pivotal.io<mailto:rokumar(a)pivotal.io>> Reply-To: "Discussions about Cloud Foundry projects

The best we have to offer is the API package in CLI https://github.com/cloudfoundry/cli This is a private API implementation, and as such we wake no promises about stability. In fact, we promise it

Hello, I am developing CF dashboard in Golang that will communicate with the cloud controller for REST call. I saw there is cfoundry <https://github.com/cloudfoundry-attic/cfoundry> a ruby gem that