Hi Yitao, I would recommend either using manual networks, or following the GitHub issue Ben R created above to see if the BOSH team can figure out the root cause of this issue with dynamic

Rather than continue this discussion here I've created an issue stating my case here: https://github.com/cloudfoundry-incubator/executor/issues/17 Mike

Hi Troy, I agree that we should bring our buildpack implementation up to date with Heroku's by adding the .profile runtime hook. Also, I believe Eric Malm had some thoughts on this hook, and how we

I think many of the use cases *could* be dealt with by multi-buildpack support or in a forked buildpack which executes the desired commands. However, the point of the feature is to allow the addition

Thanks, Mike. If source-side processing is the right place to do that \u2028-to-newline substitution, I think that there could also be a config option on the dropsonde library to have its LogSender

Credit to Jan Dubois, who actually drafted the document, and who will be helping me respond to your comments in the document. I'll provide concrete use cases where possible. The ones I have

Thanks for the insight Jim. I still think that the Executor is the place to fix this since multi line logging isn't a Loggregator limitation it is a log inject limitation which is owned by the

Hi Sylvain, It looks like your problem might be that one or more of the consul certificates in your cf manifest is not a valid PEM encoded certificate, or the certificates are missing entirely. Do

For those who have pipelines that run DEAs and HM9000, you will need to update your manifest to include certificate information. For CF users that consume releases, this will only apply once it makes

In traditional environment, we have massive physical servers hosting database and indexing engines (e.g. solr). How can we achieve similar results with small footprint but large number of

Hi Anuj, This isn't going to work as you have a v231 database and the code from v214, which doesn't contain the migrations between. Also, it's doing a migrate up, not a migrate down. While the

Hi, currently I am running CF v231 and for some reason want to downgrade/rollback to CF 214 - while trying to do that I am getting below mentioned error with API VMs ============= Error

Hi, What does cf push do in the background ? What all steps are done by cf push. Regards, Ankur

Hi Troy, Thanks for putting together this proposal. I added some comments/questions to the document. I would love your feedback/response on those. Most of the comments are concerned with the lack of

Got it. Thanks for the links to the commits, appreciate it. wrote:

GIt by sri eeo olold lollipop look Kim o gift forgot guitarists u my look ed On 12 Apr 2016 21:37, "Sylvainl Gibier" <sylvain(a)munichconsulting.de> wrote:gfggkuflg gigg.org/deploying/aws/cf-stub.html

Thanks Amit. If using dynamic network, the OpenStack support allocate ip address, using the ip address to configure metron_agent and launch vm, will it possible solve the issue? --

For the DEA's, I think it was removed here [1] with the removal of `vcap/component`. For health manager, I believe it was removed here [2] when the `cfcomponent` dependency was removed. In both

These are env. variable in Go you can easily get it with os.Getenv(" VCAP_SERVICES") or you can use go-cfenv [1] as helper. [1] https://github.com/cloudfoundry-community/go-cfenv/

Thanks for the clarification Danny. I guess the point I was trying to make earlier with the "oracle_library" buildpack use case, is that this feature has some potential functional commonality with