I have a manifest.yml that includes:

resource_pools:
- name: common
network: default
stemcell:
name: bosh-vsphere-esxi-centos-7-go_agent
version: 3262.8
cloud_properties:
cpu: 2
disk: 614400
ram: 16384

When the VM is instantiated, I note that the disk space is allocated to the /tmp filesystem. I have a /var/vcap/store filesystem that I would rather have this disk space assigned to. Is this something that I can address in the manifest file? Or, is this something inherent to the stemcell? Or, is it something for which I have to go to the code that builds the bosh resource? Or something else?

Many thanks,
Steve

This behavior is hard-coded in the bosh-agent preinstalled by the stemcell
(code
https://github.com/cloudfoundry/bosh-agent/blob/develop/platform/linux_platform.go#L779).
Recent work has gone into mounting /tmp from the ephemeral disk and allow
larger disks (work https://www.pivotaltracker.com/story/show/117177967),
but there's not currently an option to switch it to the persistent disk.

On Mon, Sep 12, 2016 at 3:40 AM, Steve Amerige <
linuxfoundation(a)serverscience.com> wrote:

I have a manifest.yml that includes:

resource_pools:
- name: common
network: default
stemcell:
name: bosh-vsphere-esxi-centos-7-go_agent
version: 3262.8
cloud_properties:
cpu: 2
disk: 614400
ram: 16384

When the VM is instantiated, I note that the disk space is allocated to
the /tmp filesystem. I have a /var/vcap/store filesystem that I would
rather have this disk space assigned to. Is this something that I can
address in the manifest file? Or, is this something inherent to the
stemcell? Or, is it something for which I have to go to the code that
builds the bosh resource? Or something else?

Many thanks,
Steve

--
Danny Berger