On Fri, Nov 28, 2014 at 1:22 PM, Andrija Panic <[email protected]> wrote:
> if you just add storage tag it will just have a tag attached to it. This > single change will not be your solution and also will not cause issues. > > Thanks for the clarification > If no compute/storage offerings are referencing that tag - that just means > that the volume might/will also be placed on that primary storage and also > on other prim storages. > > When you shutdown VM - there is button called "Migrate Instance to another > primary storage" > I don't really want to migrate, I just want to prevent this primary storage from having further allocations to it > So this is what you might want to use... > > Also, when new volumes should be deployed, cloudstack should detect that > your first storage is full, and skip it, and search for another one, if I'm > not mistaken... > You can just lower tresholds to i.e. 80%, so no new volumes will be created > if the storage is over 80% full - thus you have space to grow existing > volumes... > Take overprovisioning into account... > > That's a part of the problem. Overprovisioning is set rather high, due to them being auto expanded, but I guess I have to reduce this a bit to prevent disasters. Thanks again! -- Erik > On 28 November 2014 at 10:26, Erik Weber <[email protected]> wrote: > > > I currently have two primary storages, where one of them are getting > full. > > Thus I need to prevent further allocations to it. > > > > Is it enough to add a storage tag to it, or will that mess up existing > > volumes? > > > > -- > > Erik > > > > > > -- > > Andrija Panić >
