If a storage pool is put in disabled state then it will not be picked up as a possible destination when a volume is being migrated or when a virtual machine is being migrated along with its volumes.
Regards, Devdeep > -----Original Message----- > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > Sent: Monday, February 23, 2015 7:44 PM > To: dev@cloudstack.apache.org > Cc: us...@cloudstack.apache.org > Subject: Re: Disable primary storage, not delete... > > Yeah, probably option 2 is better. > > I would think you couldn't use this primary storage as the target of a > migration or for HA. > > On Monday, February 23, 2015, Harikrishna Patnala < > harikrishna.patn...@citrix.com> wrote: > > > 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.si...@citrix.com > > <javascript:;>> 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.tutkow...@solidfire.com > > <javascript:;>] > > >> Sent: Monday, February 23, 2015 3:48 AM > > >> To: dev@cloudstack.apache.org <javascript:;> > > >> Cc: us...@cloudstack.apache.org <javascript:;> > > >> 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.tutkow...@solidfire.com <javascript:;>> > > >> 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.pa...@gmail.com > > <javascript:;> > > >>> <javascript:_e(%7B%7D,'cvml','andrija.pa...@gmail.com > > >>> <javascript:;>');>> > > 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.tutkow...@solidfire.com <javascript:;> > > >>> <javascript:_e(%7B%7D,'cvml','mike.tutkow...@solidfire.com > > <javascript:;>');> > > >>> 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 <javascript:;> > > >> 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>*™*
