Hi Andrija,
thanks for your effort, that is some good and bad news at once.
The good thing is, we are not too stupid to set it up.
I will get in contact with NetApp and hear what they say, I’m afraid it gonna
take some time…
Regards
Christian
> On 13. Sep 2019, at 00:00, Andrija Panic wrote:
Hello,
Going back to "unable to start MV due to insufficient capacity" errors
Is there a way to turn these off as I can overprovision for "CPU" but not "# of
CPU Cores"?
CS ver 4.11.0.0
Thanks
Adam
Disclaimer Notice:
This email has been sent by Oakford Technology Limited, while we have check
Hi Christian,
I work at NetApp. I can contact you off list to give you instructions on how to
get support at NetApp involved.
Thanks, Andrija, for debugging!
Talk to you later,
Mike
On 9/13/19, 1:15 AM, "[email protected]"
wrote:
NetApp Security WARNING: This is an exte
Cool - would be happy to learn that the issue is solved - want to make
after that the proper documentation upstream.
Thx Mike!
On Fri, Sep 13, 2019, 07:19 Tutkowski, Mike
wrote:
> Hi Christian,
>
> I work at NetApp. I can contact you off list to give you instructions on
> how to get support at
Hi Adam,
That insufficient capacity exception message has probably nothing to do
with the number of CPU cores (and most of the time with anything
capacity-related, it's just that we are lazy to pass the real error to as
the API reaponse...) but is a general message that can mean 100 different
thin
Christian,
In the meantime, you can try the *SolidFireShared *plugin, which I just
tested and it seems to works fine - this means one huge LUN/datastore for
hosting all ACS volume (you can make Primary Storage per cluster)
(FYI, this is different than the 1-2-1 "SolidFire" plugin in the sense that
