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)?

For a bit more information on how Windows does containerization (hint: it doesn't involve a rootfs), you can check out a recent blog post from the Greenhouse

sorry JK - it's still early am (ignore what I just said) - the stack is the specific rootfs - the container image is a combination of a droplet plus a stack. The container image will then run in your

Hey JK, a stack is a combination of the rootfs and droplet. This is conceptually a "container image" that will then run in your garden container. For a windows stack you would need a windows vm/cell

Thank you, Amit. Is it correct to say that a stack (in the `cf stacks` sense) is a combination of rootfs + stemcell? If you have a "base VM" of, say, Linux -- and if that's the one bosh is deploying

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

How the pws / cloud-ops team verify the buildpack checksum before deploying it ?

Oh interesting! I was thinking about creating a broker that can do same thing, Are you looking to open source this broker? 

Hi JK, I don't work on any of these parts of Cloud Foundry but I can give a very basic overview: [1] rootfs: the filesystem used for applications deployed on Cloud Foundry. The current default is

No, we are trying to focus on development of the V3 API, we will only fix major issues with the V2 API. Thanks, Nick