cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harikrishna Patnala <harikrishna.patn...@citrix.com>
Subject Re: Disable primary storage, not delete...
Date Mon, 23 Feb 2015 12:37:08 GMT
Hi,

I think it is better to go with option 2, as it makes sense to be part of one of the states.

I believe that VMs using that storage continue to work, but what are the plans for the operations
related to the storage on those VMs like migration/HA/... ? 

Thanks,
Harikrishna

On 23-Feb-2015, at 3:01 pm, Devdeep Singh <devdeep.singh@citrix.com> wrote:

> Hi,
> 
> I was looking into implementing the ability to disable a storage pool for provisioning.
I could think of two ways to do it
> 
> 1. CloudStack admin could add a 'disabled' tag on the storage pool. The storage pool
allocators would skip the pools for allocating volumes with the 'disabled' tag. 
> 2. Other option would be to add 'Disabled' as one of the states of storage pool. This
could be a state in addition to "Up", "Maintenance" etc. A storage pool in "Disabled" state
will not be picked up for provisioning volumes. This would require new apis for disabling/enabling
storage pool.
> 
> Thoughts, comments?
> 
> Regards,
> Devdeep
> 
>> -----Original Message-----
>> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
>> Sent: Monday, February 23, 2015 3:48 AM
>> To: dev@cloudstack.apache.org
>> Cc: users@cloudstack.apache.org
>> Subject: Re: Disable primary storage, not delete...
>> 
>> For my suggestion to work, though, your compute and disk offerings have to
>> be set up currently to make use of one or more storage tags.
>> 
>> The idea is then that these offerings would require your primary storage to
>> have a given tag or tags and it never will (effectively disabling that primary
>> storage from being used with your offerings).
>> 
>> On Sunday, February 22, 2015, Mike Tutkowski
>> <mike.tutkowski@solidfire.com>
>> wrote:
>> 
>>> What about changing the storage tags field of your primary storage so
>>> it doesn't serve as a match for any compute or disk offering?
>>> 
>>> On Sunday, February 22, 2015, Andrija Panic <andrija.panic@gmail.com
>>> <javascript:_e(%7B%7D,'cvml','andrija.panic@gmail.com');>> wrote:
>>> 
>>>> Hi folks,
>>>> 
>>>> I was wondering is it safe to change the Cluster Wide primary storage
>>>> to a Zone Wide primary storage (change the database,
>>>> cloud.storage_pool). This is ACS 4.3.0
>>>> 
>>>> 
>>>> Or actually better question - since I have some old NFS servers exist
>>>> as Primary Storage - is there any way to exclude this NFS (Cluster
>>>> Wide)  - or disable it, so the new Volume Uploads will not use that
>>>> NFS storage...
>>>> 
>>>> This is some trail from the history, that I can't really delete, but
>>>> would like to completely disable further usage of this NFS server...
>>>> if possible at all...
>>>> 
>>>> THanks,
>>>> 
>>>> 
>>>> --
>>>> 
>>>> Andrija Panić
>>>> 
>>> 
>>> 
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkowski@solidfire.com
>>> <javascript:_e(%7B%7D,'cvml','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>*™*

Mime
View raw message