I noticed that some REST actions can be performed via JSON calls, and some via XML. The REST API Browser is a collection of XML calls, and I found that there is only a limited number of JSON methods comparing to XML. Since JSON is easier to call and parse using python, I was wondering if 1) there is any more advanced (hidden) doc for JSON calls, 2) there is a possibility to somehow translate XML to JSON calls, 3) there would be some consistency maintained in future releases of UCSD API (JSON=XML).
Not exactly sure, but I know what you are experiencing. It's annoying to have to keep custom JSON and XML parsers available in your favorite REST API calling language (in my case, PowerShell). I, too, would like to see some consistency, but I'm pretty sure what we are seeing is anything XML related was created long ago and never bothered to be updated, while JSON related returns are relatively newer in the product's lifetime.
I also see that with the Body of the API calls too. Some take full example examples while others take JSON in the body of the REST API URI.
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: email@example.com)
Please watch video for more details: