Hi CF Dev team, I am just starting to look into how web sockets based app can run in a cloud foundry env. If you have any reference links/wiki's that walk thru this web sockets working, will help

Hi Eric - please ignore last message - I found the issue - I installed diego with collocated VM as well as other VMs - which make CC confuse and collocated VM was not having all the functionality/jobs

Well I *thought* I had put in a universal link. Here is one <https://docs.google.com/spreadsheets/d/1QOCUIlTkhGzVwfRji7Q14vczqkBbFGkiDWrJSKdRLRg/edit?usp=sharing> . I've also responded to all your

Same here, seems like the document is not publicly readable? Warm regards Marco

Hi Eric – Thanks for trying to help me to resolve my issues – please check comments inline: => Database issue was in manifest, which got resolved once I update/changed the log_level value from

I'm asked to sign in to Google account to read the Roadmap. Is this an intentional behavior? Thanks in advance. Jim Campbell wrote ----- I'm not a ... noburou taniguchi -- View this message in

Please read the documentation http://docs.cloudfoundry.org/deploying/common/consul-security.html wrote:

I'm afraid I don't understand your situation, but can't you use User-Provided Service [1]? If you can build a PostgreSQL instance where you can access it with psql and where a CF app instance can

hi, when i deploy cf-release, consul agent job failed start, i found the err log in the vm. == Starting Consul agent... == Error starting agent: Failed to start Consul server: Failed to parse any

Hi, Tom, That's correct, Diego final release versions 0.1438.0 and later currently support staging Docker images only from v2 Docker registry APIs. Garden-Linux final release 0.327.0 and later also

Hi, Tom, Thanks for the update. Sounds like we'll have to make sure that the consul_agent job template is present on all the CC VM types in all the cf-release manifest generation templates and

Hi, Anuj, Thanks for the info, and sorry to hear you've run into some difficulties. It sounds like Cloud Controller is getting a 503 error from the nsync-listener service on the CC-Bridge. That most

Hi, I wish to confirm, diego(v0.1441.0) only pulls from v2 registry now and not backward compatible with v1? What diego version switched out versions? Thanks, Tom

Hi Eric, Thank you. These questions sent me in the right direction. On the CC VM: To be clear, this vm is labeled api_z1, where I got the log from, and running cloud_controller_ng. No consul was

Abacus will want to support plans in its resource config (as mentioned in issue #153 https://github.com/cloudfoundry-incubator/cf-abacus/issues/153) Starting with a basic approach, there would be a

Hi, Tom, Thanks for the logs. From the getaddrinfo error in the CC logs, it looks like CC is unable to resolve the nsync-listener service via Consul DNS on the expected nsync.service.cf.internal

Thanks. We are not running Diego. So writing an app seem to be the most viable option. wrote: -- http://www.twitter.com/sivabalans

hi, i'm trying to have a third party validate a uaa jwt (https://getkong.org/plugins/jwt/), and it is rejecting the uaa token because it doesn't have the "typ" claim on it. i kno "typ" is optional,

Regarding Nic's ssh comment, if you're running Diego, I'd recommend using the port forwarding feature instead of copying the data. It was actually one of the scenarios that drove the implementation of

Hey Mike, I'm discussing with the PWS teams if there's a good way to announce that info. Best, Amit