1. Tagging @LeoD in case he know. but i thin PS goes under the SDK as the PS module is now part of it. and i don't see it under Virt in currently in the community
https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/bd-p/sdk-and-api-discussions
https://mysupport.netapp.com/NOW/download/software/nmsdk_dotnet/9.4/
2. in my scripts either open multiple connections in one of these ways (Prefer the first one)
$NCClustersNames = "clu01","clu02"
$NCClusters = Connect-NcController -Name $NCClustersNames -Credential (Get-Credential)
OR
$NCClusters = @{}
$NCClusters.clu01 = Connect-NcController -Name "clu01" -Credential (Get-Credential)
$NCClusters.clu02 = Connect-NcController -Name "clu02" -Credential (Get-Credential)
And use it as
Get-NcVol -Controller ($NCClusters | ? name -eq "clu01")
OR
Get-NcVol -Controller $NCClusters.clu01
OR - when i want the data from all the clusters (for the first option only):
Get-NcVol -Controller $NCClusters
3. see here https://practical-admin.com/blog/netapp-powershell-toolkit-101-volume-snapshots/
$query = @{
Name = $volName
}
$attributes = @{
VolumeSnapshotAttributes = @{
SnapshotPolicy = $policyName
}
}
Update-NcVol -Query $query -Attributes $attributes
4. I think yes, working with SSH output is not fun, here someone actually formatted for you the outputs and inputs of thousands of commands.
As a person who work with the top four vendors SDK's, it seems to me that NetApp has the most advanced PS Module out there, that is most compliant to the PS standards and really has almost 1:1 mapping between every API command they have to the PS one.
is it perfect? - Not, but i see vendors releasing PS Modules that their own commands dosen't pipe to one another, and the parameters has different name in each cmdlet.
Gidi