cf-dev@lists.cloudfoundry.org

Re: Php build pack offline version availability

Hey James, Thanks for replying. Yes for the option 1, I did the same thing for the building. I could see the below on the screen: AMISHISH-M-91EG:php-buildpack ashah$ BUNDLE_GEMFILE=cf.Gemfile

By Amishi Shah · #1079 ·

Re: Java Buildpack v3.1.1

Hi, They package 1.8.0_51 based on build 16. This is true for each of the OSs listed in the release notes. Chris. Christopher Frost - Pivotal UK Java Buildpack Team

By Christopher Frost · #1078 ·

Re: Java Buildpack v3.1.1

Hi Chris, Are you able to confirm which build of OpenJDK has been included for each OS? We’re waiting on a Kerberos bug fix that arrived in OpenJDK

By Jones, Daniel · #1077 ·

Re: CF push error - Not able to resolve - Error dialing loggregator server: Get https://loggregator.systemdomain.com

The buildpacks didn't successfully upload, so you'll probably just need to "bosh restart api_z1/0" which should cause the startup script to upload them. Joseph CF Release Integration Team

By CF Runtime · #1076 ·

Re: FYI: CAB call for July 2015 - moved to 7/15 @ 8a PDT

Thanks a lot Amit for this detailed write up. This is much clearer now. Guillaume.

By Guillaume Berche · #1075 ·

Re: Is Garden limiting disk IOs ?

Thanks Will. I guess with Garden moving to runC, the migration will bring disk io limits, would be nice to record that somewhere in a story so that this does not get forgotten. I was about to start

By Guillaume Berche · #1074 ·

Re: App autosleep support

Hi Guillaume, We have a similar motivation for such feature request for saving resources. We tried that our with a quickly implement POC and made similar experience as you have written in the

By Klevenz, Stephan <stephan.klevenz@...> · #1073 ·

Re: CF push error - Not able to resolve - Error dialing loggregator server: Get https://loggregator.systemdomain.com

I just disabled - source/destination checks And able to curl 'google.com' now from private IP. Should I need to again do - bosh deploy ? -- Regards, Ronak Agarwal (M) +91 8446044994 (O) +91 20

By Ronak Agarwal <roagarwa@...> · #1072 ·

Re: CF push error - Not able to resolve - Error dialing loggregator server: Get https://loggregator.systemdomain.com

If I restart my NAT vm and do curl google.com - I am getting response. When I try ssh to any of the private VM (api_z1 IP) from this NAT vm -> ssh -i "bosh.pem" vcap(a)10.10.17.0 " It is required

By Ronak Agarwal <roagarwa@...> · #1071 ·

Re: CF push error - Not able to resolve - Error dialing loggregator server: Get https://loggregator.systemdomain.com

Thanks Joseph. I am not clear at one point - I already have a NAT vm which I had just stopped and again started, so are you asking me to create a new NAT vm because I have stopped it earlier? because

By Ronak Agarwal <roagarwa@...> · #1070 ·

Re: CF push error - Not able to resolve - Error dialing loggregator server: Get https://loggregator.systemdomain.com

Yeah, without the NAT vm nothing will be able to get out to the internet. They will be able to respond to external requests, such as a request to the api, or the login server, or an individual app.

By CF Runtime · #1069 ·

Re: CF push error - Not able to resolve - Error dialing loggregator server: Get https://loggregator.systemdomain.com

I tried 'curl http://google.com' from my api_z1 instance but was unable to get any response. I create my NAT vm through 'bosh aws create' command, but by mistake I stopped that VM on AWS. So does

By Ronak Agarwal <roagarwa@...> · #1068 ·

Re: CF push error - Not able to resolve - Error dialing loggregator server: Get https://loggregator.systemdomain.com

It looks like the api instance is unable to upload the buildpacks to the blobstore. Perhaps the NAT (network NAT, not message bus NATS) instance is not configured correctly. Are you able to curl an

By CF Runtime · #1067 ·

Re: CF push error - Not able to resolve - Error dialing loggregator server: Get https://loggregator.systemdomain.com

Its a fresh install. I found few logs may be helpful to resolve this issue -- I found few logs on cloud_controller_ng as below - Nodejs buildpack install fail

By Ronak Agarwal <roagarwa@...> · #1066 ·

Re: Is Garden limiting disk IOs ?

The honest answer there is that I'm not sure. It's conceivable that limiting CPU for a container could prevent it from pummeling disk enough to DOS a garden host, but we've not tested that. I'll talk

By Will Pragnell <wpragnell@...> · #1065 ·

Re: CF push error - Not able to resolve - Error dialing loggregator server: Get https://loggregator.systemdomain.com

Btw CF-213 is a fresh install or update ??

By Gwenn Etourneau · #1064 ·

CF push error - Not able to resolve - Error dialing loggregator server: Get https://loggregator.systemdomain.com

Hi, Please go through all my instance info below and let me know what can be done to resolve this issue?? I have deployed CF-213.yml release through microbosh on AWS. I have installed latest CF CLI

By Ronak Agarwal <roagarwa@...> · #1063 ·

Re: AWS deployment manifest with HAproxy

Also Stephen, the templates by default attempt to use an ELB named cfrouter. So if you want to try to use an ELB again, just create one with that name and when you deploy BOSH should connect it to

By CF Runtime · #1062 ·

Re: AWS deployment manifest with HAproxy

Hi Stephen, You generally never want to alter the manifest templates unless you're making a PR with general improvements to the templates. Customizing your own deployment should be done either

By Amit Kumar Gupta · #1061 ·

Re: Any problem with cloudfoundry.org?

I can access them now. Thanks! Tushar Dadlani wrote -- View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Any-problem-with-cloudfoundry-org-tp1018p1027.html Sent from the CF Dev

By Noburou TANIGUCHI · #1060 ·

Messages