You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Matt Spurlin <ma...@appcore.com> on 2014/06/20 15:30:49 UTC
Volume Instance IDs
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
RE: Volume Instance IDs
Posted by Suresh Sadhu <Su...@citrix.com>.
As mike said .. when we deploy a vm ,root disk will be created with instance id(root-3) id and this the number is increases sequentially when we deploy more instances .
Like first system vm s get instance id as 1,2 for cpvm and ssvm with root disks tagged with instanced id like root-1 for cpvm,root-2 for ssvm and later router and guest vms gets next incremental ids .
Data disks will be created with the whatever name we provided.
Regards
Sadhu
-----Original Message-----
From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
Sent: 20 June 2014 23:08
To: dev@cloudstack.apache.org
Subject: Re: Volume Instance IDs
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.tutkowski@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
> <ma...@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.tutkowski@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.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*
Re: Volume Instance IDs
Posted by Mike Tutkowski <mi...@solidfire.com>.
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.tutkowski@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 <ma...@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.tutkowski@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.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*
Re: Volume Instance IDs
Posted by Mike Tutkowski <mi...@solidfire.com>.
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 <ma...@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.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*