UCSD's PowerShell Agent and Invoke-WebRequest/Invoke-RestMethod
Now, if this is in fact as designed, I'd really REALLY love for it to actually show up in the documentation. Otherwise, you might have people (like myself) trying to figure out what the hell to do with 800-1000 lines of code we've written for various functionality.
Re: UCSD's PowerShell Agent and Invoke-WebRequest/Invoke-RestMethod
Never mind. I seem to have figured out there's something wrong with the PowerShell PSSession the PSA seems to spawn. I can nest a New-PSSession within that session and everything works fine. I did resort to stop using Invoke-RestMethod and did JSON and XML conversions of output coming back from Invoke-WebRequest (specifically the Content property) and doing what I needed to do. Will likely be logging this as a question (along with the hope that this gets escalate for bug fix).
In this article, we are providing sample work flows for the private cloud management solution. In our topology, ACI is used for network. We have placed the BMA outside the UCS fabric and connected through L3 switch. The UCS ser...
This workflow will log onto a WLC and find the connected AP(s) and test if they are on the network.
Validated on UCSD 126.96.36.199
This came together via several parties of people (Sasha, Russ and Michael Z.)
The original question was this:
When deploying open automation connector module and trying to create side menu per UCSD docs
This contribution was provided by: Sabina Al Farah.
Many thanks go out to Sabina Al Farah.
2 Workflows are attached :
Ceph - Setup Cluster - using Ansible - on RHEL
Ceph - Provision Block Storage
This is an integration example between UCSD and Cohesity.
Posted for Russ (Please direct questions to: firstname.lastname@example.org)
Please watch video for more details: