Yeah, that would be the minimum required. Then, I would add: (3) override the recursors to be used by consul. With those 3x options, consul can be configured to support any scenario without having

Hi All, I have put together a slide deck explaining a few routing use cases based on my understanding of the traffic flows in Cloud Foundry. Please feel free to point out any missing/erroneous flows

It was a pleasure to work with Jim as well as colleague and as OSS contributor (firehose-to-syslog). Jim always help us to bring the best to the loggregator.

We're planning on the next cf-release bump. At this time, both formats are supported, to allows the change to happen.

At what version does this change occur?

Hi Everyone, We have made changes to the way *uaa.scim.users* and *uaa.scim.groups* can be specified in the deployment manifest. The *previous* format for uaa.scim.users was: -

Hello all, Jim Campbell, the Project Lead for the Loggregator team within the Runtime PMC, last day at Pivotal was this week. We wish him well in his future endeavors and thank him for his time with

Hi, Jiaxin, Let's handle these cases separately. When you shut down a DEA or a Diego Cell gracefully (say, as BOSH does when updating or deleting a VM), it will attempt to get replacements for its

when you use bosh to update the runner vm, the instances will automatically migrate to another runner vm. You need to make sure you have enough vm(to be more specifically the resources ) to hold

I want to increase runner VM or delete runner VM. When I increase runner VM , I wish to make instances running on different VMs. When I delete runner VM , I wish to migrate instances from that VM to

Dingo PostgreSQL is a service broker that offers dedicated HA PostgreSQL clusters running in Docker containers, deployed & upgraded by BOSH. Continuously archiving all day long to Amazon S3. Batteries

CVE-2016-5016 UAA accepts expired certificatesSeverity High Vendor Cloud Foundry Foundation Versions Affected - Cloud Foundry release v239 and earlier versions - UAA release v3.4.1

have you checked loggregator tc logs? and make sure you have configured cert related info correctly -- Regards, Yitao

Hi all, Can anyone help me with this? Regards, Abhik Sent: Monday, August 15, 2016 7:01 PM To: Discussions about Cloud Foundry projects and the system overall.

I suspect that if you pushed the app before setting the backend to default to diego, the app's state in the DB still has backend: dea. So CC is trying to schedule it on the DEAs and the first

This is so so awesome. Great job!

cf v240, diego 0.1481.0, cflinuxfs-rootfs 1.21.0, etcd 63, garden-linux 0.339.0, bosh-openstack-kvm-ubuntu-trusty-go_agent 3262.4 With a runner instance, pushing the sample go application works

Thanks Stefan!

Hi, Am 17.08.2016 um 18:49 schrieb Senthil Velusamy: For Cloud Foundry you can take a look at the Pivotal documentation: https://docs.pivotal.io/pivotalcf/1-7/customizing/start-stop-vms.html#stop It

,All, We have deployed BOSH / cloudfoundry on vSphere. There are two hosts (each host is an availability zone) and vm's are distributed between these two hosts. microBOSH, BOSH and cloudfoundry all