I've spun up UCS Director and created my first VM via automation - woo! Now I'm confused as to how my users can access it. I configured UCSD to deploy a VM with Windows 2008 R2, and it successfully mounts the ISO. However, it's waiting on user input at the VMware console.
Is this as far as a standard catalog can go? Can it complete the Windows installation and give it an IP address, or does that require a VM image? Trying to learn
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 18.104.22.168
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: