Customizing RHEL7 VM Template for UCSD Self-Service?
We're developing a proof of concept for self-provisioning VMs through UCS Director.
The basics are all there and our non-privileged users can create and destroy VMs. We're trying to figure out what the best practices are for allowing the requesting users to actually connect to their new VM, when the VM in question is a Red Hat Enterprise Linux 7.1 or 7.2 install.
Do people rely on vSphere customization and tie that into UCSD workflows for login credentials, run VIX scripts or something similar, or hard-code user credentials into the template, use Webmin, or do something else?
Any references to successful techniques or documentation on best practices would be greatly appreciated.
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 22.214.171.124
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: