Thanks a lot!!! 2017-02-03 19:06 GMT+01:00 David Sabeti <dsabeti(a)pivotal.io>:

Hi Leandro, I've been holding off on defaulting to the Diego backend primarily because we planned to make that change when we shipped cf-deployment <https://github.com/cloudfoundry/cf-deployment>.

guys is there any reason why Diego is not enabled by default in the `generate_deployment_manifest` templates? AFAIK DEA arch is being deprecated in a few months so I think it could be good to already

Hello everyone, we already had an internal discussion on the topic and since we could not quite come to a solution, I'd like to ask in this list. We're using a self-made

Hi All, On behalf of the entire UAA team I am pleased to announce the release of *UAA 3.10.0*. This release truly has been community driven effort with major feature contributions from *SAP* and

Thanks Adam for the permissions. The linked “Inception notes” document [1] seems to also have problems with permissions. Could you please also take care of that? Thanks and warm

When TLS is enabled on Gorouter (router.enable_ssl: true; false by default), it will currently accept connections using SSLv3, TLSv1.0, TLSv1.1, or TLSv1.2. The HAProxy in cf-release always has TLS

Shannon, I agree with Mike - we're in a similar situation where we already have implemented all network ACLs and FW rules - so also for us access control would be the priority, and partitioning nice

Hi All - In our continued effort for a clean the Loggregator code base we are moving another repo outside of Loggregator. The bosh-hm-forwarder can now be found at the following locations. New

fyi... Since I got access to the CF Public Calendar (thanks Chip!) I moved the two recurring meetings (CAB and CF-extensions) to that calendar. CAB:

Hi All - Just a reminder. Today is the last day to update your reference to the statds-injector. We'll be deleting the version in the Loggregator repo today. You need to use this repo

Hi All - I have updated the sharing settings. Everyone should now be able to see and comment. Thanks Adam

Hi, all, In order to streamline, expedite, and control the quality of extensions proposal, we have created a process by which all proposal must adhere. I am asking your feedback on this process so

Dear Adam, thanks for sharing the document. Could you please make it accessible for everyone? All I currently get is "You need permission Want in? Ask for access, or switch to an account with

FYI... Find summary of meeting here: https://docs.google.com/document/d/1RCMHYFQaB1oqdEKev-cVF2Rrr6qqCT9C6RmFFKmUxnI Best, dr.max ibm cloud labs sillicon valley, ca usa maximilien.org Sent

Cancel

Hi All - The loggregator team is planning a track of work that results in some architectural changes to how syslog drains are implemented. I wanted to share our plans and solicit any feedback about

Quick followup, we may have spoken too soon about the changes to the TPS job. Those changes are not slated to be in cf-release v252, but rather the release following it. Please leave

In the upcoming cf-release (v252), some components communicating with CC via its internal API (for example: Loggregator, BBS, and TPS) will do so over mutual TLS. This is part of an effort to have all

Hi, Anyone that wants to join me & Max is more than welcome. Just use one of the ways below. Online meeting: https://apear.in/cf-abacus Slack channel: abacusdev.slack.com Phones: Participant