(you can also hack the DB... just saying...) On Tue, 29 Jun 2021 at 17:20, Rakesh Venkatesh <www.rakeshv....@gmail.com> wrote:
> Thanks all for the response. I was on 4.14 and didnt see this. will check > it in 4.16 > > On Tue, Jun 29, 2021 at 5:12 PM Wei ZHOU <ustcweiz...@gmail.com> wrote: > > > yes. > > > > There is an icon on the UI which does exactly the same. > > > > -Wei > > > > On Tue, 29 Jun 2021 at 16:16, Wido den Hollander <w...@widodh.nl> wrote: > > > > > > > > > > > Op 29-06-2021 om 15:44 schreef Rakesh Venkatesh: > > > > Hello folks > > > > > > > > Is there a way to disable a particular storage pool so that it won't > be > > > > used for further volume allocation? I don't want to enable the > > > maintenance > > > > mode as that will turn off the VM's whose volumes running on that > > pool. I > > > > don't want to use a global setting also since this will come into > > effect > > > > after the threshold value is reached. > > > > > > > > In some cases even if the pool is just 10% allocated, I still want to > > > > disable it so that the current volumes will keep existing on the same > > > pool > > > > and at the same time further deployment of volumes on this pool is > > > disabled. > > > > > > > > I looked at the storge tags options but that involves adding tags to > > > > service offerings and I dont want to mess up with that tags. Should > we > > > add > > > > a new api to enable this feature? or any other better suggestion? > > > > > > > > > > See: > > > > > > https://cloudstack.apache.org/api/apidocs-4.15/apis/updateStoragePool.html > > > > > > The 'enabled' flag does exactly what you want: > > > > > > 'false to disable the pool for allocation of new volumes, true to > enable > > > it back.' > > > > > > Wido > > > > > > > > > > > -- > Thanks and regards > Rakesh venkatesh > -- Andrija Panić
