Thanks Chris. Will keep you posted on how it goes. Sumanth Sent: Monday, July 06, 2015 8:16 PM To: Discussions about Cloud Foundry projects and the system overall. Subject: Re: [cf-dev] revrse proxy

Hi Sumanth, We recently added support for "Context Path Routing" <https://docs.google.com/document/d/1H_adSiY7wGR85av9YfxxPRylSO8Q8U0ANJJTg6wpYRQ> in both the GoRouter and CC

The main goal is to have a mapping from a top level url like abc.com/app1 abc.com/app2 getting mapped to the actual routes given by cf to the respective apps. So I was thinking of adding a reverse

What is the goal of your reversed proxy? Did you mean load balance of multiple instances of an app (cf push APPNAME -i 3 ==== having 3 instances of APPNAME)? Gorouter knows how to dispatch to app 1

Hi, In an environment with multiple micro services being deployed in CF. Does the "go router" have the functionality of reverse proxy or should I configure httpd to sit in front of the go

Hi Peter, Actually `cf restage` does cause down time. It will stop existing instances, stage the new app bits with the buildpack, and start new instances. It's possible that your app may start

Hi again Gianluca, To follow up from the previous email - we have added this to our investigation into a possible handshake problem between TC and our library; we'll be investigating either way.

Hi Gianluca - apologies for the delay; everyone here has been out on holiday (and/or watching the world cup.) We were originally investigating this issue as part of a separate bug - but again,

Hi All, All the documentation and github code (manifest stubs) deal with deploying diego with bosh-lite. Are there any pointer/docs for generating an openstack manifest for diego deployment using

Following up on James's description of the "papertrail" ssh audit traces that the diego-ssh support is adding. This is very useful to have these traces. Can you confirm these traces are provided

Hi, please find my feedback to this thread *short version:* 1- need preserve good CF experience with HTTP only (direct SSH flow is still blocked and a pain in many organisations) => +1 to preserve

hi Erik did you have the chance to open the chore on this case? if yes, are there any news about? thx for your help Gianluca

Hello, We use some user-provided services to provide some configurations to our apps. Sometime we need to update the configurations but without downtime. So we update these configs using cf

Hi Joseph & Zak, actually we have deleted the bosh deployment as well as dropped the uaa and cc db;s.. Then did the fresh 202 deployment and top of that we have moved to v210 successfully. As per

Thank you, James. I've read them and probably understood what's in progress. The pdf in the latter URL is very helpful. -- View this message in context:

Simply deleting the schema_migrations table entries may allow the api to start, but the actual changes from those migrations will need to be rolled back manually too. Best thing is certainly to

I believe that those limits would only need to be increased if you have more than 256 warden containers on a single server. Is that the case? Joseph & Zak CF Runtime Team wrote:

Hello all, We have just moved the gorouter and routing-api components from src/{gorouter, routing-api} to src/github.com/cloudfoundry/gorouter and src/ github.com/cloudfoundry-incubator/routing-api

One of the goals of V3 is that we are exposing a few internal CF concepts as domain objects in the API. Specifically droplets and packages. In V2, after you have pushed applications bits (created a

I have to agree with Matt on this one. I feel that the recycling of containers is a very anti-developer default. When you approach Cloud Foundry from the perspective of running production applications