m3 instances

[Leandro David Cacciagioni]

Hi guys!!! I'm trying to deploy Cloud Foundry using m3 instances and I'm getting the following error:

Started updating job runner_z1_2xlarge > runner_z1_2xlarge/0 (canary). Failed: Action Failed get_task: Task 558ef395-a61e-42d9-5dd2-de99ed5d5a43 result: Applying: Applying job dea_next: Applying package rootfs
_lucid64 for job dea_next: Getting temp dir: mkdir /var/vcap/data/tmp/bosh-agent-applier-packages-CompiledPackageApplier-Apply511877358: no space left on device (00:00:19)


Error 450001: Action Failed get_task: Task 558ef395-a61e-42d9-5dd2-de99ed5d5a43 result: Applying: Applying job dea_next: Applying package rootfs_lucid64 for job dea_next: Getting temp dir: mkdir /var/vcap/data/t
mp/bosh-agent-applier-packages-CompiledPackageApplier-Apply511877358: no space left on device

Is there any reason why your stemcells didn't work with m3 instances?

Thanks,

Leandro.-

[Dmitriy Kalinin]

m3 instance types work; however, they do have very small ephemeral disks (http://aws.amazon.com/ec2/instance-types/#m3). if you need larger ephemeral disk you can configure your resource pool with ephemeral_disk: {type: gp2, size: <anything>} (http://bosh.io/docs/aws-cpi.html#resource-pools) to use custom sized ebs volume.

To unsubscribe from this group and stop receiving emails from it, send an email to bosh-users+...@cloudfoundry.org.

[Leandro David Cacciagioni]

Thanks Dmitry