When you deploy a VM, a root disk will be created for it automatically. I imagine the instance ID of this root volume will be that of the VM.
On Fri, Jun 20, 2014 at 11:36 AM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > When you create a volume in the GUI, as well, it will not have an instance > ID. > > Once you attach the volume to a VM, this is when the volume gets an > instance ID (the association between the volume and the VM that "owns" it > at the time being). > > Now, I'm not sure I understand what one would do if one wanted to apply a > clustered file system to such a volume and have it accessible to multiple > VMs (who are hopefully coordinating access to the data on the volume). I'm > guessing CloudStack doesn't support this? > > > On Fri, Jun 20, 2014 at 7:30 AM, Matt Spurlin <matt.spur...@appcore.com> > wrote: > >> I have been poking around at the code for deploying VMs and noticed >> that it appears volumes need an instance ID in order to be chosen as a >> suitable volume for the VM. When I create a volume through the API it >> does not have an instance ID. How do volumes get this instance ID? >> Thanks, >> Matt >> > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the cloud > <http://solidfire.com/solution/overview/?video=play>*™* > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud <http://solidfire.com/solution/overview/?video=play>*™*
