asgard
asgard copied to clipboard
Add block device mapping support
Currently, custom block device mappings are not able to be communicated via the cluster creation endpoint in AutoScalingController.groovy (and subsequently applied to the LaunchConfiguration).
I see there has been past discussion about default and/or hardcoded block device mappings:
ASGARD-1078 ASGARD-1153 ASGARD-1152 ASGARD-1124
Would a patch with backend support for this be accepted?
This would be handy (as well as the ability to configure a default block device mapping). The new m3 types now have instance storage but ONLY if you launch the instances with a block device mapping specifying that the ephemeral disks are mapped. Tying the mapping to the AMI doesn't seem to be enough for these guys (and the documentation seems to confirm)