I'm just wondering if anyone else is running into the same issues I'm having with USC Director. Basically I have 2 types of vm's a user can check out - 'free' and 'paid'. A paid VM would have to go through an approval workflow, while a free vm would not need to go through approval, however there would be an additional workflow on the free vm that would automatically set the Lifecycle of the vm to 2 weeks (a paid vm can live forever, but a free vm can only last 2 weeks to prevent sprawl).
Here's what I've done so far:
I created 2 different VDC's (free and paid), as I want my free vms in a different vlan and limit it to 50 ips as well as have the approval workflow.
I created two different catalog items (free and paid) and in the free catalog I execute a post provisioning workflow to set the lifecycle.
They both use the same template, and all is good. However, the problem is if a user clicks on the 'paid' catalog they can then change the VDC to the free vdc which then bypasses the post provisioning worklow so the vm can live forever as well as bypass the approval workflow.
Is anyone else doing anything life this? Am I just completely missing something? If I could just lock the VDC on the catalog then I would be ok - it would be a pain to create the catalogs for each group but I could at least live with it. Right now there is just no way I can roll this functionality to everyone as someone would figure it out quickly to get a free vm forever.
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 184.108.40.206
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: