Also worth noting:
Both ec2 and openstack have a concept of having a separate ephemeral disk attached to the instance as it boots.
For ec2 the number of attached disks and their size varies with instance types:
http://aws.amazon.com/ec2/instance-types/
For openstack, you can define a single ephemeral disk of varying size, which is attached but not mounted by default afaict.
For azure, it seems like a default temporary disk 'D' is created but I can't find any information about its configurability or default size.
Handling ephemeral disk constraints should be implemented as a separate feature.
Also worth noting:
Both ec2 and openstack have a concept of having a separate ephemeral disk attached to the instance as it boots.
For ec2 the number of attached disks and their size varies with instance types:
http:// aws.amazon. com/ec2/ instance- types/
For openstack, you can define a single ephemeral disk of varying size, which is attached but not mounted by default afaict.
For azure, it seems like a default temporary disk 'D' is created but I can't find any information about its configurability or default size.
Handling ephemeral disk constraints should be implemented as a separate feature.