Hey Tomoe Great question. I would also prefer disaster recovery to be possible via "bosh stop" then "bosh start". This is almost possible in etcd, except for the conditional you found. The reason for

Not quite. For one, each elastic cluster would generally be a separate BOSH deployment. So to leverage links, it would require cross-Director links. Also, the current work in BOSH links and BOSH DNS h

Hey Nic, No, this is service discovery between system components. There would be a CC in the management tier and a Diego BBS in an elastic cluster. Currently these things talk to each other over Consu

Sorry about that, here's the link: https://docs.google.com/document/d/1ynyE6g85NQ4rEp3tuNB0ZPakAxCiC7UxsrRevcJPcAQ/edit?usp=sharing wrote:

Hi all, A while back, the Infrastructure team sent out a proposal for how to implement service discovery between elastic clusters, as part of the elastic clusters feature narrative. We have a second r

Hi Tom, Apologies for having had several releases with "N/A" under the OpenStack stemcell. We had a very lengthy process of obtaining a working OpenStack environment from our provider. While waiting f

Hi Nithiyarsi, Check out https://docs.cloudfoundry.org/devguide/deploy-apps/troubleshoot-app-health.html#start *Make sure your application code uses the PORT environment variable. Your application may

Hi Graham, Something like that would be nice. However, technically, every test needs admin because in their Before hooks they use the admin to create an org, quota, etc. Sounds like what you want is t

+cf-bosh

Hi Graham, Your approach sounds good. What you are doing/plan to do in CI sounds perfect, as well as your plan for production (namely, run what you have in CI except cf-acceptance-tests). In the READM

You should not copy any of the etcd data (neither Diego's etcd cluster, nor the etcd cluster used by Loggregator and Routing components). It's not only unnecessary since CF is designed to seamlessly r

+cf-bosh mailing list it-services(a)marcoristuccia.com> wrote:

Hi J K, To add to what Nick said: You can think of Garden as a generic API for something that creates containers and runs processes in them, and can be backed by various different backend implementati

Awesome! wrote:

Hi Layne, There are three main Cloud Foundry-related organizations in GitHub: cloudfoundry, cloudfoundry-incubator, and cloudfoundry-community. Each organization has many repositories. If there is a s

Separate VM not necessary, you need a consul server cluster though, can't just have consul agents in client mode. Your server cluster can be colocated with other VMs, and the servers can act as client

Your first job has consul services, so you'll need to colocate the consul_agent there too. You also don't have any consul servers running anywhere. TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> w

Thanks Dan, So it sounds like *if* your router has public IPs, then you need to tell those IPs to the UAA so it knows to trust them and handle the x-forwarded-* headers from them. Going back to Johann

Hi Benjamin, Re bumping consul: Yes, soon: https://www.pivotaltracker.com/story/show/113007637 Re updating confab so that people can tweak their consul settings directly from BOSH deployment: Currentl

Hi all, Every week, I see a user confused by the domain, system_domain, and app_domains properties in the Cloud Foundry manifest. The confusion is primarily around domain and system_domain. These prop