On behalf of the Lattice team, I am pleased to welcome v0.3.3 of Lattice! Lattice v0.3.3 is a follow-on release, firming up Buildpack support and polishing the CLI. If you're using Lattice v0.3.0,

The CF Routing team has begun collaborating with the CAPI team on support for Route Services in Cloud Controller, and soon we will begin work on support for TCP Routing (and multiple container

Hi, We think this message was dropped and so we are posting it again. How long of a timeout are you seeing? The gorouter and ha_proxy have a default timeout of 15 minutes. If you are using an ELB or

Erik, That's very helpful, thank you! Qing

Hi R M, We think that this message may have been lost so we are resending it. Are you able to deploy other applications? This error seems to stem from mounted disk problems. Could you see if the

Hi Owais, We think this message may have been lost so we are sending it again. We compiled one back in December, I can't think of anything that would have changed since

When the cloud controller instances come up, they install any buildpacks configured in the manifest. If you want a buildpack NOT to be replaced automatically (because you've updated it yourself),

steps: 1. replace php_buildpack 2. stop all components by "nova stop" 3. start all components by "nova start" 4. check php_buildpack I expected it was the version in step 1. However, step 4 got the

Hello, I am trying to setup Cloud foundry environment on Eclipse, so that I can make java project and deploy them directly to the Cloud Foundry(Server), But due to mismatch in different plugin

I am getting error while running data-dog-nozzle - https://github.com/cloudfoundry-incubator/datadog-firehose-nozzle go run main.go -config

What do you mean by "after restarting cf"? How are you doing that? There's a lot of components, which one or ones are you restarting? What steps are you running? Dan wrote:

Hi all, We tried to update the default buildpacks with a new version. However, after restarting cf, the old version comes back. (See below) It seems all the default buildpacks will be ensured to be

Hi Qing, First, Ops Metrics is a closed-source addition to Pivotal Cloud Foundry. The metrics exposed by Ops Metrics today come from the collector[1] and tomorrow from both the collector and

i'm glad you found it! i'll make sure that amit gupta sees this report as he is currently PM for the MEGA team that is responsible for the DEAs. thanks for sharing the results. -- Thank you, James

Finally, I find out the problem, but may not the one I said above. It seems a little bug exsited. In my deployment, it will install some buildpacks by default, but perhaps caused by some network

yes, it work before.

Hi, You never change the password right ? it was working before ?

Is refresh token always returned, for all the grant types ? It seems to be the case for authorization_code grant type but I don't think it is returned for client credentials

Hi all, We've recently announced CF Summit events for both Berlin and Shanghai, and we'd love your participation! Berlin will be on November 2nd and 3rd, 2015 > http://berlin2015.cfsummit.com/ The

Hi Mike Thanks for addressing my questions gain. I agree that it's important to make both the rootfs and the buildpacks backward-compatible with each other. People often use master branch of the