Diego Container Disk Limit

[rjain-pivotal]

The maximum_app_disk_in_mb sets the maximum amount of disk a user can request. Why do we have this setting across the deployment. We have apps that are of varying sizes, 1G, 2G , 4G etc. So we would prefer to have an uncapped or arbitrary high setting and the executor/scheduler allocating disk based on actual consumption or from the manifest file. And for charge back we can use Space and Org Quotas.

I don't see similar settings in other container schedulers, wondering what is the design decision to have this setting.

Thanks, Rajesh

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/150608954

The labels on this github issue will be updated when the story is started.

[emalm]

Hi, @rjain-pivotal, as I explained privately, that's a setting on Cloud Controller that determines the maximum disk allocation an app instance can declare. Diego itself has no particular maximum, although if a unit of work requests more disk than any individual cell advertises it will not be capable of being placed.