I recently upgraded from Juju 1.18 to 1.18.1, and suddenly my charm to deploy a MapR hadoop cluster stopped working. I traced the problem to the fact that non-root disks are no longer associated with the instances, even though the constraints to the juju-deploy option have not changed.
As far as I can tell, there is not yet a juju constraint that defines non-boot storage. The documentation for the root-disk constraint specifically notes "Additional storage that may be attached separately does not count towards this value."
- What changed ? The default m1.xlarge instances have 1 or 2 ephemeral disks when I create them within the basic ec2 commands ... but not when Juju creates them
- What is the Juju-supported mechanism for defining additional storage volumes.