Modify already provisioned VMWareVM vNIC IP configuration via cloupia method (static ip configuration)
I'm looking after the possibility of modifying the IP configuration (IP Address, Gateway, etc) of the vNIC of an already provisioned VMWareWM: basically I would like to put a static IP configuration in place. I'm aware of the possibility of using the vSphere PowerCLI, anyway I would also like to obtain the desired result without using the Powershell agent.
After digging into the cloupia sdk, I found a static method of the VMWareService class through which I managed to create an object of type VMVNic (representing the vNIC of an actual VM) and modify its IP Address via the concerned set method. After that I supposedly should persist the change and there is actually another static method in VMWareService class for that, which anyway fails with a not very explanatory error message.
Is what I'm trying to achieve feasible at all? In case yes, is my approach correct or rather should I use a different one based on different classes and methods?
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 188.8.131.52
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: