You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Mike Tutkowski <mi...@solidfire.com> on 2013/03/14 07:00:22 UTC
Local versus Shared Storage Type for Compute Offering
Hi,
I was a little surprised to see the Storage Type field when creating a
Compute Offering recently.
The options are Local or Shared.
I guess I was thinking that if you had a preference for a VM running on
local storage of the hypervisor or using shared storage that you would
specify this using the Storage Tags field.
Can someone explain this a bit to me? What if you said Local for the
Storage Type, but put in a single Storage Tag that was only associated with
shared storage?
Thanks!
--
*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: Local versus Shared Storage Type for Compute Offering
Posted by David Nalley <da...@gnsa.us>.
On Thu, Mar 14, 2013 at 2:00 AM, Mike Tutkowski
<mi...@solidfire.com> wrote:
> Hi,
>
> I was a little surprised to see the Storage Type field when creating a
> Compute Offering recently.
>
> The options are Local or Shared.
>
> I guess I was thinking that if you had a preference for a VM running on
> local storage of the hypervisor or using shared storage that you would
> specify this using the Storage Tags field.
Whether an instance will use local or shared storage is defined in the
service offering.
>
> Can someone explain this a bit to me? What if you said Local for the
> Storage Type, but put in a single Storage Tag that was only associated with
> shared storage?
>
It would deploy to local storage and ignore the unavailable tag. (it
will not adhere to the 'tag' in such a case, apparently the preference
is to deploy to a less-than-preferred resource rather than fail -
whether that's correct behavior or not is debatable, but that is
current state (unless something has changed recently))
Re: Local versus Shared Storage Type for Compute Offering
Posted by Mike Tutkowski <mi...@solidfire.com>.
Hey guys,
This is great info - thanks!
I admit, however, that I still don't understand why we have the
shared/local storage type for Compute and Disk Offerings. It seems like
you could accomplish this with tagging. For example, if you only want the
Offering deployed to local storage, then use a storage tag that is
associated with local storage.
What am I missing here?
Thanks!
On Thu, Mar 14, 2013 at 12:34 AM, Nitin Mehta <Ni...@citrix.com>wrote:
> I don¹t think this behavior changed ever.
> The reason for the hard check should be as follows
>
> Imagine the tag is for premium offering and the customer is paying premium
> for that. Now he says deploy vm with this offering and say there is no
> host with premium tag left to deploy the vm.
> Now if we don't fail the deployment and instead accommodate it in a
> different host other than premium it would be breaking customer promise
> and he would still be paying premium which is not good.
>
> Thanks,
> -Nitin
>
> On 14/03/13 11:55 AM, "David Nalley" <da...@gnsa.us> wrote:
>
> >On Thu, Mar 14, 2013 at 2:20 AM, David Nalley <da...@gnsa.us> wrote:
> >> On Thu, Mar 14, 2013 at 2:18 AM, Koushik Das <ko...@citrix.com>
> >>wrote:
> >>> See inline
> >>>
> >>>> -----Original Message-----
> >>>> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> >>>> Sent: Thursday, March 14, 2013 11:30 AM
> >>>> To: cloudstack-dev@incubator.apache.org
> >>>> Subject: Local versus Shared Storage Type for Compute Offering
> >>>>
> >>>> Hi,
> >>>>
> >>>> I was a little surprised to see the Storage Type field when creating
> >>>>a Compute
> >>>> Offering recently.
> >>>>
> >>>> The options are Local or Shared.
> >>>>
> >>>> I guess I was thinking that if you had a preference for a VM running
> >>>>on local
> >>>> storage of the hypervisor or using shared storage that you would
> >>>>specify this
> >>>> using the Storage Tags field.
> >>>>
> >>>
> >>> Storage type in compute offering is for root disk of VM (whether needs
> >>>to be created on local storage or shared). Based on this validation are
> >>>also made as to what all operations are permitted on the VM, disks.
> >>> Storage tags are only used for placements when there are multiple
> >>>options available for either local or shared storage.
> >>>
> >>>> Can someone explain this a bit to me? What if you said Local for the
> >>>>Storage
> >>>> Type, but put in a single Storage Tag that was only associated with
> >>>>shared
> >>>> storage?
> >>>>
> >>>
> >>> In this case deployment should fail
> >>>
> >>
> >> Has something changed recently with how we treat tags? As of 3.0.x we
> >> would disregard the tag if we couldn't deploy to the tagged resource.
> >> (/me goes to try this in 4.0.x)
> >>
> >> --David
> >
> >Koushik,
> >
> >You are correct. I wonder when this changed.
> >
> >--David
>
>
--
*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: Local versus Shared Storage Type for Compute Offering
Posted by Nitin Mehta <Ni...@citrix.com>.
I don¹t think this behavior changed ever.
The reason for the hard check should be as follows
Imagine the tag is for premium offering and the customer is paying premium
for that. Now he says deploy vm with this offering and say there is no
host with premium tag left to deploy the vm.
Now if we don't fail the deployment and instead accommodate it in a
different host other than premium it would be breaking customer promise
and he would still be paying premium which is not good.
Thanks,
-Nitin
On 14/03/13 11:55 AM, "David Nalley" <da...@gnsa.us> wrote:
>On Thu, Mar 14, 2013 at 2:20 AM, David Nalley <da...@gnsa.us> wrote:
>> On Thu, Mar 14, 2013 at 2:18 AM, Koushik Das <ko...@citrix.com>
>>wrote:
>>> See inline
>>>
>>>> -----Original Message-----
>>>> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
>>>> Sent: Thursday, March 14, 2013 11:30 AM
>>>> To: cloudstack-dev@incubator.apache.org
>>>> Subject: Local versus Shared Storage Type for Compute Offering
>>>>
>>>> Hi,
>>>>
>>>> I was a little surprised to see the Storage Type field when creating
>>>>a Compute
>>>> Offering recently.
>>>>
>>>> The options are Local or Shared.
>>>>
>>>> I guess I was thinking that if you had a preference for a VM running
>>>>on local
>>>> storage of the hypervisor or using shared storage that you would
>>>>specify this
>>>> using the Storage Tags field.
>>>>
>>>
>>> Storage type in compute offering is for root disk of VM (whether needs
>>>to be created on local storage or shared). Based on this validation are
>>>also made as to what all operations are permitted on the VM, disks.
>>> Storage tags are only used for placements when there are multiple
>>>options available for either local or shared storage.
>>>
>>>> Can someone explain this a bit to me? What if you said Local for the
>>>>Storage
>>>> Type, but put in a single Storage Tag that was only associated with
>>>>shared
>>>> storage?
>>>>
>>>
>>> In this case deployment should fail
>>>
>>
>> Has something changed recently with how we treat tags? As of 3.0.x we
>> would disregard the tag if we couldn't deploy to the tagged resource.
>> (/me goes to try this in 4.0.x)
>>
>> --David
>
>Koushik,
>
>You are correct. I wonder when this changed.
>
>--David
Re: Local versus Shared Storage Type for Compute Offering
Posted by David Nalley <da...@gnsa.us>.
On Thu, Mar 14, 2013 at 2:20 AM, David Nalley <da...@gnsa.us> wrote:
> On Thu, Mar 14, 2013 at 2:18 AM, Koushik Das <ko...@citrix.com> wrote:
>> See inline
>>
>>> -----Original Message-----
>>> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
>>> Sent: Thursday, March 14, 2013 11:30 AM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: Local versus Shared Storage Type for Compute Offering
>>>
>>> Hi,
>>>
>>> I was a little surprised to see the Storage Type field when creating a Compute
>>> Offering recently.
>>>
>>> The options are Local or Shared.
>>>
>>> I guess I was thinking that if you had a preference for a VM running on local
>>> storage of the hypervisor or using shared storage that you would specify this
>>> using the Storage Tags field.
>>>
>>
>> Storage type in compute offering is for root disk of VM (whether needs to be created on local storage or shared). Based on this validation are also made as to what all operations are permitted on the VM, disks.
>> Storage tags are only used for placements when there are multiple options available for either local or shared storage.
>>
>>> Can someone explain this a bit to me? What if you said Local for the Storage
>>> Type, but put in a single Storage Tag that was only associated with shared
>>> storage?
>>>
>>
>> In this case deployment should fail
>>
>
> Has something changed recently with how we treat tags? As of 3.0.x we
> would disregard the tag if we couldn't deploy to the tagged resource.
> (/me goes to try this in 4.0.x)
>
> --David
Koushik,
You are correct. I wonder when this changed.
--David
Re: Local versus Shared Storage Type for Compute Offering
Posted by David Nalley <da...@gnsa.us>.
On Thu, Mar 14, 2013 at 2:18 AM, Koushik Das <ko...@citrix.com> wrote:
> See inline
>
>> -----Original Message-----
>> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
>> Sent: Thursday, March 14, 2013 11:30 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Local versus Shared Storage Type for Compute Offering
>>
>> Hi,
>>
>> I was a little surprised to see the Storage Type field when creating a Compute
>> Offering recently.
>>
>> The options are Local or Shared.
>>
>> I guess I was thinking that if you had a preference for a VM running on local
>> storage of the hypervisor or using shared storage that you would specify this
>> using the Storage Tags field.
>>
>
> Storage type in compute offering is for root disk of VM (whether needs to be created on local storage or shared). Based on this validation are also made as to what all operations are permitted on the VM, disks.
> Storage tags are only used for placements when there are multiple options available for either local or shared storage.
>
>> Can someone explain this a bit to me? What if you said Local for the Storage
>> Type, but put in a single Storage Tag that was only associated with shared
>> storage?
>>
>
> In this case deployment should fail
>
Has something changed recently with how we treat tags? As of 3.0.x we
would disregard the tag if we couldn't deploy to the tagged resource.
(/me goes to try this in 4.0.x)
--David
RE: Local versus Shared Storage Type for Compute Offering
Posted by Koushik Das <ko...@citrix.com>.
See inline
> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> Sent: Thursday, March 14, 2013 11:30 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Local versus Shared Storage Type for Compute Offering
>
> Hi,
>
> I was a little surprised to see the Storage Type field when creating a Compute
> Offering recently.
>
> The options are Local or Shared.
>
> I guess I was thinking that if you had a preference for a VM running on local
> storage of the hypervisor or using shared storage that you would specify this
> using the Storage Tags field.
>
Storage type in compute offering is for root disk of VM (whether needs to be created on local storage or shared). Based on this validation are also made as to what all operations are permitted on the VM, disks.
Storage tags are only used for placements when there are multiple options available for either local or shared storage.
> Can someone explain this a bit to me? What if you said Local for the Storage
> Type, but put in a single Storage Tag that was only associated with shared
> storage?
>
In this case deployment should fail
> Thanks!
>
> --
> *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>
> *(tm)*