Hi, Stanley,

If you're looking to reduce the Diego VM footprint in a dev deployment, you
could consider using the 'colocated_vN' (N=1,2,3) jobs in the manifests
generated by the spiff-based scripts in diego-release. They pack all the
jobs in diego-release (and garden and etcd) onto a single VM, so you could
deploy with 1 instance of colocated_z1 and 0 instances of all other jobs.
If you need more container capacity in that deployment, you can then
increase the instance count of the cell jobs from 0 (you will have one cell
already via the existing colocated job instance).

Also, as a warning, the Diego team doesn't regularly test the colocated-VM
deployment configuration, so it's possible that it may accidentally break
in the future (or even that it's broken now!). So I wouldn't recommend its
use in a production deployment.

I can't speak to the current state of colocatability of the jobs in
cf-release, or to the status of the community cf-boshworkspace project.

Best,
Eric, CF Runtime Diego PM