yes, there has been a typo. Thank you for pointing out ! The correct CVE number is : *CVE-2016-3084* Thanks, Sree Tummidi Sr. Product Manager Identity - Pivotal Cloud

Hi Chip, I think there might be a typo here as the CVE reference seems to be the same as for the UAA persistent XSS vulnerability. G

CVE-2016-0781 UAA Password Reset VulnerabilitySeverity Low Vendor Cloud Foundry Foundation Versions Affected - Cloud Foundry release v236 and earlier versions - UAA release v3.3.0 and

-What information were you trying to understand from mem_used_bytes? We used mem_used_bytes and mem_free_bytes (currently metrics from bosh) to get an overview over the real overall memory usage of

You need to bundle install the gem in the staging container. The build pack would generally do this. Dan lingeshmouleeshwaran(a)gmail.com> wrote:

Hi Dan , yes I have installed the require gem via *bundle install* to specify the path of vendor staging directories which is available in below paths /var/vcap/data/packages/dea_next/*

lingeshmouleeshwaran(a)gmail.com> wrote: This is the way you should be doing it. What about this doesn't help / work for you? Dan

When 234 was released, we did not realize that Collector was creating additional metrics. Based on reports, we have added back any missing metrics that people felt were needed. Let me know if we

Thanks DHR and Sunil , @ DHR , I have followed your way to install the gem on staging directory , but it doesn't help. is this same way followed by existing cloudfoundry java buildpack ?? @ Sunil

Nick, The last two seem to be too strict. A user should be able to remove themselves from spaces as long as the organization has an OrgManager who has the power to reassign users to the space in the

Hi Cloud Foundry, We have a request from an API client that would like for users to be able to remove themselves from an Organization or Space. This allows self-service without the app obtaining an

Looks like the Runtime team took some out in v234, added them back in in v235. From the Runtime Slack: ​ wrote: -- Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963

Yep, I've had a back thread with Runtime OG who now has the DEA metrics and who I thought had implemented all previous /varz (aka Collector) metrics into the firehose. No answer from Mr Fraenkel

Including Jim Campbell to make sure this reaches him.

Hi, by upgrading to CF v234 (including pre-release v232) we lost all our monitoring capabilities regarding DEA and HM9000 (we were still using Collector). By migrating to Firehose only a fraction of

Hi Rootfs is not specific to an os flavor to mention in Windows it's referred as rootdsk This is the base volume which comes when a vm is created Since more people work on Unix flavor to generalise

Hi Enable cloning with repo an make auto update enabled this there is no need to install lingeshmouleeshwaran(a)gmail.com> wrote: -- Thanks & Regards Sunil Babu K C +91-81970-35608

I think you'd be better to get the gems to be deployed inside the buildpack zip & used by your buildpack bin scripts from when the zip is unpacked. Maybe you could vendor the gems as part of your

Hi Cloudfoundry , Is there any simple way, we can update or install new libraries in existing cf stacks (cflinuxf2) without creating new custom stacks ?? *Example :* Our modified java buildpack not

Is it correct to say that in the context of CF, `rootfs` is a Linux-only abstraction, and is not necessarily relevant to Garden (whereas it may be relevant to one or more of the Garden backends)?