EBS volumes can only have one instance attached at one time, so I'm not sure they are a good analog for services which can be related to many things. This is why I think storage is fundamental, and needs to be modeled at the provider level.
Until then, a stop gap would be to add an ensemble sub-command to pre-create a machine, then use this branch:
EBS volumes can only have one instance attached at one time, so I'm not sure they are a good analog for services which can be related to many things. This is why I think storage is fundamental, and needs to be modeled at the provider level.
Until then, a stop gap would be to add an ensemble sub-command to pre-create a machine, then use this branch:
https:/ /code.launchpad .net/~clint- fewbar/ ensemble/ reuse-machines/ +merge/ 67417
To assign a deployed service to the machine after you have resized its EBS root or attached any extra EBS volumes to it.