ache.org>" <
> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> Date: Friday, 29 September 2017 at 6:57 PM
> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <
> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org&
dstack.apache.org>>
Date: Friday, 29 September 2017 at 6:57 PM
To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
mailto:dev@cloudstack.apache.org>>,
"us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>"
mailto:us...@cloudstack.apache.org&
: Friday, 29 September 2017 at 6:57 PM
To: "dev@cloudstack.apache.org" ,
"us...@cloudstack.apache.org"
Subject: Re: Advice on converting zone-wide to cluster-wide storage
Hi Andrija,
I just took a look at the SolidFire logic around adding primary storage at
th
Hi Mike,
thx for that info, that is exactly what I also see as DB differences, but
was also wondering if anyone played with it in Production :)
Will wait for some more reply hopefully !
Cheers
Andrija
On 29 September 2017 at 15:27, Tutkowski, Mike
wrote:
> Hi Andrija,
>
> I just took a look a
Hi Andrija,
I just took a look at the SolidFire logic around adding primary storage at the
zone level versus the cluster scope.
I recommend you try this in development prior to production, but it looks like
you can make the following changes for SolidFire:
• In cloud.storage_pool, enter the ap
