Hi,
Apologies if this question isn't appropriate to this forum as the problem may be more my lack of .Net knowledge than anything else but I'm trying to use the DataONTAP powershell module from within a C# windows application I'm writing to automate/simplify some operational checks we currently run manually (snapmirror lags, snapshot space, vol usage, etc).
I'm trying (for example) to connect to a controller (using the Connect-NaController cmdlet) and return it as an NetApp.Ontapi.Filer.NaController object. In previous powershell scripts we've produced we've done wrapped that in a function, called it at the start of the script and used the resultant $filer variable as the -Controller parameter when calling subsequent cmdlets like Get-NaSnapmirror, GetNaVol, etc.
#Connects to and returns a NetApp Filer controller object
function ConnectNAFiler($filerfqdn)
{
try
{
$filer = Connect-NaController $filerfqdn -ErrorAction "stop"
$filername = $filer.Name
$filerport = $filer.Port
$filerprot = $filer.Protocol
Write-Log "Successfully connected to $filername`:$filerport via $filerprot"
}
catch
{
Write-Log "Unable to connect to $filerfqdn - Exiting"
CleanUp
Write-Log "### Exiting $me ###"
break
}
return $filer
}
In my limited grasp of C# I go add the DataONTAP module to my session, create a runspace, invoke Connect-NaController and see that I get back a PSObject with a base type of [0] = "NetApp.Ontapi.Filer.NaController" and I can enumerate properties just as I would in PS. My stumbling block from here is how would I use that object in subsequent cmdlets later in the managed code? Can I just store it somewhere and append as a parameter as in PS?
class DataONTAP
{
public static void ConnectNAFiler()
{
InitialSessionState initialSession = InitialSessionState.CreateDefault();
initialSession.ImportPSModule(new[] { "DataONTAP" });
Runspace runspace = RunspaceFactory.CreateRunspace(initialSession);
runspace.Open();
RunspaceInvoke invoker = new RunspaceInvoke(runspace);
Collection<PSObject> results = invoker.Invoke("Connect-NaController myfiler");
foreach (PSObject ps in results)
{
Debug.WriteLine(ps.Properties["name"].Value);
Debug.WriteLine(ps.Properties["port"].Value);
Debug.WriteLine(ps.Properties["protocol"].Value);
Debug.WriteLine(ps.Properties["version"].Value);
}
}
}
Is this even worthwhile? I've seen some great examples in the manageability SDK to using the APIs to do this kind of thing but we'd like to go down the "C# managed PS" route to 1) preserve our investment in what we've done in PS and 2) we're hearing that stuff like the Exchange 2010 tools and the AD Admin Center are just wrappers for PS code.
