Hi All,
I have a requirement which I need to change the number of network interfaces assigned to vSphere (vCenter) machine dynamically during the provisioning stage. For example a vm blueprint should be able assign 1, 2, or 3 network interfaces with different network profiles.
Kindly assist with my requirement.
Thanks in advance.
-Sajithru
Very simple and quick matter using a combination of SovLabs Property Toolkit and one of the IPAM providers. The IPAM profile has built in which NIC and which subnet profile to use. Based on a request form input field, property toolkit can eval that and add a property group based on that. "if field.x == input.x then attach prop.group.Y" If you're not using SovLabs, it's still possible, but you're developing all the code and logic yourself, then managing it. People that have done that are probably not coming forward to just hand it over to you on a silver platter.
Very simple and quick matter using a combination of SovLabs Property Toolkit and one of the IPAM providers. The IPAM profile has built in which NIC and which subnet profile to use. Based on a request form input field, property toolkit can eval that and add a property group based on that. "if field.x == input.x then attach prop.group.Y" If you're not using SovLabs, it's still possible, but you're developing all the code and logic yourself, then managing it. People that have done that are probably not coming forward to just hand it over to you on a silver platter.
Well, AFAIK nothing you can do when you submit request - event broker is able to catch it when allocation phase already passed (in allocation phase vra already "planned" a new machine with all pre-configured networks, addresses etc). You may have a post-provisioning workflow to re-configure machines (call Resource Action --> reconfigure with new NICs).
Adding NICs works in EBS after the allocate phase because there's no resource calculation involved there. It takes a little doing, but that is one thing Property Toolkit solves with no custom code required.
daphnissov
Hmm, interesting... so if i add subscription with stuff like virtualMachineAddOrUpdateProperties.put('VirtualMachine.NetworkX.Name','network-1) where NetworkX (X from 1 to 16) vra will add those NICs to the machine (event VMPSMasterWorkflow32.Requested -- PRE)?
You need more properties than that, and there are other things happening behind the scenes. Most of the customers I work with have the Property Toolkit, so I don't fool with rolling it from scratch.
daphnissov
I got it, ToolKit is great and i would love to have it but - there is an ugly reality where i have to live and work
Back to my question - lets exclude ip address assignment (pretend that DHCP takes care of all those things - i don't need ugly vCAC address allocation process) - will vra make new NICs for my machine? Beside to solve problems i like to learn new stuff to better understand how everything works. If i have a million $ i would definitely hire PSO
Um, I don't know where you're getting the idea that this would take $1M in PSO. It actually takes no PSO at all...you just buy it and plug it in.
Yes, to answer your question, vRA is capable of adding those NICs dynamically at request time.