#vserver create - avoid certain nodes/aggregates
1 messages · Page 1 of 1 (latest)
I don't think that is possible. You need to update the list of aggregates every time you add a new aggregate to the system. It's something that probably doesn't happen that often, and it's very easy to automate
After the svm is created you can certainly modify/update the aggr-list option to indicate allowed aggregates but I do not recall if it’s allowed at svm creation
yes thanks, its trying to avoid the root volume being provisioned on a certrain aggr in the first place, aggrs which are reserved for certain customers.
You can always vol move the root after creating. You can ahah specify which aggregate the root volume goes in specifically when creating the svm
Hi, yes have done that in the past but this is being created using an automation front end using restapi calls so thats not what they are after.
i did find an aggregates switch within the api call which allows a list to be specified at creation which hopefully would mean that the svm root would be created on one of the list
if they have it automated already anyways, why can't they automate selecting the correct aggregate as well? 🤔