Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of andrija.panic@gmail.com
 designates 209.85.213.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACOnxCjaUqAyrUz7uWQJMVvvSm5=JED_KmpkVJv3HYKmmoHvWw@mail.gmail.com>
References: 
 <CAMvtBPOrFZbkQVs=2xYw7zYqPLP71k+x+nUduDBy16zutVxeng@mail.gmail.com>
	<CACOnxChC-3HJo3X3KsMBUUaswwzJZbHAQw2tukqMnWT3r9bAtg@mail.gmail.com>
	<CACOnxCjaUqAyrUz7uWQJMVvvSm5=JED_KmpkVJv3HYKmmoHvWw@mail.gmail.com>
Date: Mon, 23 Feb 2015 09:23:33 +0100
Message-ID: 
 <CAMvtBPOVWUyq1UJkn-S1sEMCxAUPcE6a6y7SoZBSypxv6_HcBg@mail.gmail.com>
Subject: Re: Disable primary storage, not delete...
From: Andrija Panic <andrija.panic@gmail.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Cc: "users@cloudstack.apache.org" <users@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=001a11421f2e313ba5050fbd1efc

--001a11421f2e313ba5050fbd1efc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thx Mike, but I'm not using that storage at all for compute offerings -
just as you explained, via storage tags, I use CEPH.

But my problem is - when customer uploads a volume, then the volume is
writen to randomly choosen Primary Storage, including this old NFS, that I
don't generaly use (at least for Compute/Disk Offerings)

So I just want to stop uploading volumes to this one if possible...

Thanks

On 22 February 2015 at 23:18, Mike Tutkowski <mike.tutkowski@solidfire.com>
wrote:

> For my suggestion to work, though, your compute and disk offerings have t=
o
> 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.co=
m
> >
> wrote:
>
> > What about changing the storage tags field of your primary storage so i=
t
> > 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=C4=87
> >>
> >
> >
> > --
> > *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=3Dplay>*=E2=84=A2*
> >
> >
>
> --
> *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=3Dplay>*=E2=84=A2*
>


--=20

Andrija Pani=C4=87

--001a11421f2e313ba5050fbd1efc--